Clearing V1
For Builders
The clearing core is neutral infrastructure. Exchanges, frontends, aggregators, and other protocols build on top of it, and the core is designed to reward the flow and the upkeep they bring. This is the map of what you can build, and how you earn for it.
Neutral infrastructure
The core clears. It does not run price discovery, hold the premium, or ship a UI, and that is deliberate: it leaves the venue and the interface to you. Anyone can list an exchange, run a frontend, or plug the core into another protocol, and every trade clears through the same core no matter where it starts. There is nothing to ask permission for.
Build a venue or a frontend
The premium trades on venues the core does not own, CLOBs and AMMs, so you can run one, or run a frontend on top of one. Fork a reference frontend or build your own. Whatever a trader clicks, the write, the trade, the exercise, resolves against the core, so you inherit its settlement guarantees without reimplementing them.
Earn with builder codes
Attach a builder code to the flow you route and earn a cut of protocol fees for it. The registry is on-chain in the core, so attribution is legible and portable: you integrate once and are credited on whichever venue the flow lands. See Builder codes.
Run a keeper network
Two keeper roles pay, and both are open to anyone:
- Resolutions. Open the recollateralization auction on an under-backed short and collect the finder fee. See Keepers.
- Auto-exercise. Exercise a trader's in-the-money options a set window before expiry, and take a cut of the intrinsic for it. It is the on-chain version of a broker exercising for you at the close, so a trader never loses an in-the-money option by forgetting it. Admin can require it per ticker, and a frontend that runs it gives its traders broker-grade UX and is paid for the service.
Compose it
The core is a clearing primitive, not a closed product, so other protocols build on it directly: lending against option positions, packaging structured products, routing hedges. The premium is external and the settlement is neutral, so an integrator plugs in at the layer it needs. See the Introduction.
Get started
Build against the SDK and the API. The SDK wraps the core's write and read paths; the API serves the data a venue or a frontend needs.