Why Sui
The technical properties of Sui that make an on-chain options exchange viable for the first time.
The problem with other chains
Building a professional options exchange on-chain requires three things that prior blockchains have not delivered simultaneously: a shared, permissionless central-limit orderbook; parallel execution across many independent markets; and finality fast and cheap enough for market makers to quote competitively.
Ethereum and its rollups provide composability but not throughput. An options exchange with 20 active series would process those sequentially, and gas costs alone price out professional market-making activity.
Sui resolves all three constraints at the infrastructure level.
DeepBook v3
DeepBook v3 is Sui's institutional-grade CLOB — a shared, permissionless orderbook primitive available to every protocol on the network. It is the only shared CLOB of its kind on any L1 today.
For Phasis, this matters enormously. Prior on-chain options designs were forced to either fragment liquidity across one AMM pool per series, or build and maintain a custom orderbook (which widens the audit surface and increases protocol risk). DeepBook eliminates both problems: Phasis uses one DeepBook pool per series, inheriting its matching engine, fee accounting, and liquidity aggregation with no custom matching code.
Parallel execution
Sui's object model assigns every on-chain object — including each DeepBook pool — to an independent shared-object slot. Transactions that touch different objects execute in parallel without coordination.
Phasis runs up to 60 active series simultaneously. On Sui, all 60 orderbooks process fills in parallel. On Ethereum, they would execute sequentially, reducing effective throughput by roughly two orders of magnitude. For a market maker quoting BTC calls and puts across six expiries, parallel execution is not a performance nicety — it is a prerequisite.
Sub-second finality and predictable gas
Sui's consensus protocol commits transactions in under one second on the network's current testnet, with gas costs proportional to the operations performed rather than calldata size or block competition.
For market-makers, this means:
- Quote updates are acknowledged in under a second rather than the 2–12 seconds typical on Ethereum
- Gas for a
replace_quotesbatch (cancel + place across several series) is a fixed, predictable cost, not an auction - Liquidators can act on underwater accounts without racing against block time
Move and the object model
Every Phasis data structure — registry, account, series, margin snapshot — is a first-class Move object. There are no tokenization bridges between the CLOB and the margin engine. Liquidation, oracle reads, and cross-series composability are direct object references in the same transaction.
Move's type system enforces key invariants at compile time: coin amounts cannot be doubled-counted, capabilities cannot be forged, and objects cannot be silently dropped. These properties reduce the audit surface meaningfully compared to equivalent Solidity designs.
Pyth on Sui
Settlement prices are read from Pyth Network's on-chain price feeds, which are published directly to Sui. There is no oracle bridge, no fallback server, and no off-chain price dependency at settlement time. The protocol reads the Pyth EMA price directly in the settlement transaction.
Summary
| Property | Sui | Ethereum / rollups |
|---|---|---|
| Shared CLOB | DeepBook v3 (built-in) | Must build or fork |
| Parallel orderbooks | Yes (object model) | Sequential |
| Finality | < 1 second | 2–12 seconds |
| Gas model | Per-operation | Auction / calldata |
| On-chain oracle | Pyth (native) | Chainlink / Pyth bridge |
| Move type safety | Yes | Solidity |
These are not incremental improvements. They are the baseline requirements for a professional options exchange, and Sui is currently the only chain that meets all of them.