Optionbolt | Developers

Three ways in

Use the core, our CLOB, or the whole stack.

Plug in at the layer you want. The core and matcher share is hardcoded and uniform, so no one buys better terms at scale.

Use the core only

Bring your own CLOB

Clear through the core directly with your own matching, or bring an existing venue. You are the matcher, so you keep the matcher's full 50% of protocol fees. The core keeps its hardcoded 50%.

Plug into our CLOB

Point your frontend at ours

Send orders to our open CLOB and earn the frontend cut. Our CLOB splits its 50% evenly: 25% of protocol fees to your frontend, 25% kept by the CLOB, and the core keeps 50%.

Route to the full stack

Send flow to app.optionbolt.com

The full Optionbolt stack: the core, our CLOB, and our frontend. The fastest path to live, on terms identical to building your own.

Per $1.00 of protocol fees through the full stack. The core's 50% is hardcoded and accrues to the DAO on every trade. Route through a third-party CLOB and frontend and the DAO still takes the core's 50%; the third parties keep the other 50% to split as they choose. The matcher's share routes through a builder code: uniform terms for everyone, with transparent approval, an anti-abuse gate, not a competitive one. More on the governance page.

Neutral terms, not neutral abstention

Competing can never become capturing.

We do not claim no one captures anything. The core charges a uniform protocol fee, and the DAO earns from our CLOB and frontend when a user chooses them. The check on capture is that the terms are uniform and the upper layers are optional and open: you can always route around them and clear through the core directly.

A VC-backed lab

Pressured to capture

Equity is a fiduciary duty: sustaining a valuation eventually pressures the lab to capture the protocol's revenue.
Preferential terms become a business-development lever.
The company owns the surface and keeps the upside.

A token-funded service provider

No pressure, and no lever

Funded by a token grant, not equity, so there is no fiduciary duty to capture.
The core and matcher split lives in the contract, not a deal, so terms cannot be bent.
The CLOB and frontend are open-source and forkable; a fork still clears through the core and pays the same split.
Ownership vests in the DAO.

Straight from the founder: we want to be the clearing core. We build a CLOB because without one there is no volume, and a frontend because without one there is no way to get off the ground. The fairness is not that we abstain from the upper layers, it is that the terms are hardcoded, uniform, open, and forkable, so competing at every layer can never become capturing.

The frontend layer

Ours is minimal on purpose. Win it.

Our frontend is a deliberately minimal single-route trading site (think hyperliquid.xyz, not Robinhood). A team dedicated to a great consumer product will beat it, and that is the intent: the frontend layer is open, and we want others to own it. The core is what we care about.

Compose on the core

Beyond the frontend.

The hard code in any options system is the clearing itself, and here it is already built and audited once, sitting under every strike and every expiry. Build the layer you want on top of it.

Exchanges & venues

Order books, AMMs, aggregators. Plug into the flash callbacks and compose whole fills atomically on the core, with no liquidity to bootstrap first.

Protocols on top

Lending against positions, leverage engines, wrappers, structured products. Because the core never liquidates, leverage is unbundled here, not banned, and owned by whoever chooses the risk.

Frontends & brokers

Any app with users, a wallet, an aggregator, a trading site, lists these options and earns the frontend cut on the flow it brings.

Start building

One clearing core. Build the rest, on terms no one can bend.

The SDK, read API, and integration guides ship with the testnet draft. Read where the ownership and the splits are heading, or follow along.

Read the docs How it is governed