Skip to content
Blockchain LabTHE VENTURE STUDIO

LibraryMarkets2023Design paperCorpus record

DeepBook: a central limit order book as a Sui shared object

DeepBook. Mysten Labs.

DeepBook publishes an order book implemented as shared objects on Sui, so matching is a chain transaction rather than a private server.

A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.

DeepBook publishes an order book implemented as shared objects on Sui, so matching is a chain transaction rather than a private server.
Evidence
Primary paper
Re-measured
No
Assumptions
3
Records linked
3

01 Claim ledger

What the paper is allowed to say

Each row is a sentence already in the study. The status is the same on every row: a model claim, not a live measurement.

  1. Claim 01 · Paper model

    The defect

    A shared-object order book takes the slow path of Sui's model on purpose. It needs a total order. That is not a contradiction. It is the object model working as documented.

  2. Claim 02 · Paper model

    The proposal

    DeepBook publishes an order book implemented as shared objects on Sui, so matching is a chain transaction rather than a private server.

  3. Claim 03 · Paper model

    The mechanism

    Bids and asks are objects. A match consumes them under the program's price-time rules.

  4. Claim 04 · Paper model

    The bound

    No volume is stated here.

02 Three cuts

Observation, model, falsifier

A desk does not stop at the summary. Each claim is cut three ways, using only this study's own assumptions and checks. Nothing here is a new figure.

  1. 01 The defect

    Observation

    What the study says

    A shared-object order book takes the slow path of Sui's model on purpose. It needs a total order. That is not a contradiction. It is the object model working as documented.

    Model

    What has to hold

    You are reading the DeepBook docs. Sui's object model is the layer underneath.

    Falsifier

    What would retire it

    What object is shared, and therefore ordered?

  2. 02 The proposal

    Observation

    What the study says

    DeepBook publishes an order book implemented as shared objects on Sui, so matching is a chain transaction rather than a private server.

    Model

    What has to hold

    You are reading the DeepBook docs. Sui's object model is the layer underneath.

    Falsifier

    What would retire it

    Who may place an order?

  3. 03 The mechanism

    Observation

    What the study says

    Bids and asks are objects. A match consumes them under the program's price-time rules.

    Model

    What has to hold

    No price, supply, yield, or adoption figure is added by this desk.

    Falsifier

    What would retire it

    What price rule picks the winner when two bids cross?

  4. 04 The bound

    Observation

    What the study says

    No volume is stated here.

    Model

    What has to hold

    You are reading the DeepBook docs. Sui's object model is the layer underneath.

    Falsifier

    What would retire it

    Who may place an order?

03 Sequence

One action, as an operating tape

  1. 01Bids and asks are objects. A match consumes them under the program's price-time rules.
  2. 02The book is a shared object, so it is ordered with other transactions that touch it.
  3. 03A keeper or a permissionless caller can submit the match. Who is allowed is a parameter of the version you opened.

04 Load-bearing

The argument, and where a pitch drops it

  1. What the name has to mean

    The cut

    DeepBook publishes an order book implemented as shared objects on Sui, so matching is a chain transaction rather than a private server.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    A later version number of DeepBook can change the object layout. Cite the version.

  2. What actually moves

    The cut

    The book is a shared object, so it is ordered with other transactions that touch it.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    A later version number of DeepBook can change the object layout. Cite the version.

  3. What a later deployment may change

    The cut

    A keeper or a permissionless caller can submit the match. Who is allowed is a parameter of the version you opened.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    A later version number of DeepBook can change the object layout. Cite the version.

05 Register

What has to be true

  • Model · Not re-measured

    You are reading the DeepBook docs. Sui's object model is the layer underneath.

  • Model · Not re-measured

    The document is the one at the source URL. A marketing page with the same brand is not this text.

  • Model · Not re-measured

    No price, supply, yield, or adoption figure is added by this desk.

06 Divergence

What happened after the paper

A later version number of DeepBook can change the object layout. Cite the version.

A later client, parameter set, or reward formula is a different object. Cite this paper for the mechanism. Cite a primary release for the network. This desk has not re-run the proof.

07 Pre-mortem

What to check before you use the idea

  4. 0 of 3 marked on this browser. A mark is a reading note, not a pass, a rating, or a recommendation.

08 Anatomy

The paper, in the order a builder needs

The problem it names

A shared-object order book takes the slow path of Sui's model on purpose. It needs a total order. That is not a contradiction. It is the object model working as documented.

What the design proposes

  • Bids and asks are objects. A match consumes them under the program's price-time rules.
  • The book is a shared object, so it is ordered with other transactions that touch it.
  • A keeper or a permissionless caller can submit the match. Who is allowed is a parameter of the version you opened.

How the mechanism is specified

  • Bids and asks are objects. A match consumes them under the program's price-time rules.
  • The book is a shared object, so it is ordered with other transactions that touch it.
  • A keeper or a permissionless caller can submit the match. Who is allowed is a parameter of the version you opened.

What this page does not treat as proven

  • No volume is stated here.
  • This is not Hyperliquid's book and not dYdX v4.
  • A later version number of DeepBook can change the object layout. Cite the version.

Why the desk still reads it

DeepBook publishes an order book implemented as shared objects on Sui, so matching is a chain transaction rather than a private server.

09 Lexicon

Terms, opened into the record

Shared order book
A book implemented as shared state. It is globally ordered.
Match
The transaction that consumes a bid and an ask. A resting order is not yet a trade.

10 Repository

Every linked record on this page

Underlined words open a page that already exists: a concept, a protocol profile, a failure record, or another paper. If a word is not underlined, this desk does not have a record for it.

This is Blockchain Lab's reading of a public design paper. It is not the paper, not a copy of it, and not an offer of tokens, equity, custody or a partnership. Later network behaviour can diverge from the text. Nothing here is investment, legal or technical advice.

Research status: Design paper. Last reviewed: 1 October 2026. This is a reading of a public paper, not investment, legal or security advice.