Native CLOB (spot only)
This page records a locked design direction, not an available market. No supported order-placement, cancellation, matching, settlement, fee, SDK-write, or custody path is released. Do not construct calls from historical module addresses, selectors, examples, or package symbols, and do not use testnet assets as if they had value.
Design boundary
Section titled “Design boundary”The intended base-layer market is a spot-only central limit order book. Perpetuals, margin, liquidation engines, and leveraged products are outside the native design.
If separately activated in a future release, the native module would keep order-book state in the chain state tree and expose versioned market-data reads and typed transaction calls. Activation would require matching runtime, genesis, RPC, SDK, indexer, explorer, wallet-review, audit, and end-to-end evidence. None of those statements should be inferred from a reserved address or implementation artifact.
Ordering and disclosure
Section titled “Ordering and disclosure”Any future order flow would use the standard plaintext mempool. Pending price, size, and side could therefore be visible before inclusion. There is no encrypted, sealed, private-send, or threshold-decrypted mempool lane. Deterministic DAG ordering is an integrity property; it is not order confidentiality and does not eliminate market or MEV risk.
Fair-ordering refinements and batch auctions are also unreleased designs. They must not be presented as current protections.
Public product boundary
Section titled “Public product boundary”- No public market catalog or supported market-data contract is certified here.
- No browser-wallet, desktop-wallet, Stele, SDK, MCP, or RPC flow may submit a trade from this documentation.
- No fee schedule, asset admission policy, settlement promise, or liquidity commitment is published.
- Mainnet is not running; the development testnet is value-less and resettable.