In our piece on perpetual decentralised exchanges (perp DEXs), we made the case that the majority of order book–based DEXs, such as dYdX and Hyperliquid, use an off-chain order book with on-chain settlement as a means to improve transaction fees and reduce latency at the order book stage. Maintaining an order book entirely on-chain requires every order placement, cancellation, or modification to be recorded on the blockchain, incurring gas fees and introducing latency limited by block confirmation times.
DeepBookV3 is a decentralised central limit order book (CLOB) protocol that operates using an on-chain order book. It benefits from lower fees and faster block verification times, inherited from the Sui blockchain on which it is built. DeepBook is developed by Mysten Labs, the same team that created the Sui blockchain.
As an open-source protocol, DeepBook positions itself as a Sui-native, permissionless, foundational liquidity layer that SUI built dApps can integrate into their platforms. This means applications can access DeepBook’s order-book functionality without needing to build their own matching engines. Each individual protocol can route its orders to DeepBook, which combines all of them into a single, shared pool of liquidity.
Deepbook advertises high throughput, low latency at ~390ms settlement times, and trading with minimal slippage. The Sui blockchain offers identical block finality times as low as ~390 milliseconds, fees averaging $0.002 to $0.01 USD (depending on transaction complexity), and parallel execution made possible through its custom consensus mechanism, Mysticeti-C.
Mysticeti-C, which we covered in our previous report, offers a low-latency DAG-style consensus mechanism and parallel execution. This allows DeepBook to scale high throughput which is necessary in an order book system where multiple traders will be placing trades and interacting with the protocol simultaneously. Additionally, the low ~390 ms settlement times offered by Sui are essential for Deepbook’s on-chain CLOB.
Overall, DeepBook’s ability to offer an on-chain order book while remaining competitive as a DEX is made possible by the cheaper fees and quicker block times offered by SUI’s core architecture.
Every element of Deepbook’s protocol is implemented on chain through the use of interlinking smart-contract modules built with Move, the native language of Sui, and made feasible by Sui's object model which differentiates between shared and owned objects.
In Sui everything that exists on-chain, from tokens to smart contracts, is represented as an object. Each object carries its own data and ownership information. Some objects are owned, meaning they belong to a single user and can only be modified by that user’s transactions. For example, a user’s wallet balance or an NFT would each be owned objects and only the holder of that object’s private key can change or transfer it. Other objects are shared, meaning they can be accessed or updated by multiple users at once. These include decentralised exchanges, on-chain order books, liquidity pools, and governance smart contracts where many participants interact with the same shared object.
The distinction between owned and shared objects determines which path a transaction takes through Sui’s Mysticeti consensus. Owned-object transactions use the fast path (Mysticeti-FPC) for rapid, parallel execution since they affect only one user’s state, whereas shared-object transactions must go through the Mysticeti-C path to reach full consensus. In particular the normal path will order transactions before finalising because if multiple users interact with the same shared object simultaneously, their actions may conflict or depend on one another. For example, in Deepbook multiple users can simultaneously interact with the exchange at once so transactions must be sequenced before execution so that prices, order matching, and state updates happen in the correct order.