LibraryScaling2023Design paperCorpus record
Sui Move: objects, not accounts, as the programming model
Sui Move. Mysten Labs.
Sui's Move dialect publishes objects with owners and IDs. A transaction that touches only owned objects need not take a total order with every other transaction, under the docs' rules.
A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.
Sui's Move dialect publishes objects with owners and IDs. A transaction that touches only owned objects need not take a total order with every other transaction, under the docs' rules.
- Evidence
- Primary paper
- Re-measured
- No
- Assumptions
- 3
- Records linked
- 4
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.
Claim 01 · Paper model
The defect
Object-centric is not 'faster Solana'. It is a claim about which transactions commute. Shared objects do not commute.
Claim 02 · Paper model
The proposal
Sui's Move dialect publishes objects with owners and IDs. A transaction that touches only owned objects need not take a total order with every other transaction, under the docs' rules.
Claim 03 · Paper model
The mechanism
An owned object has a single owner. A transaction on it can be certified without ordering it against unrelated owners.
Claim 04 · Paper model
The bound
This note does not quote a transactions-per-second number.
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.
01 The defect
Observation
What the study says
Object-centric is not 'faster Solana'. It is a claim about which transactions commute. Shared objects do not commute.
Model
What has to hold
You are reading Sui's object documentation. A consensus overview that skips objects has skipped the programming model.
Falsifier
What would retire it
Which objects in the transaction are shared?
02 The proposal
Observation
What the study says
Sui's Move dialect publishes objects with owners and IDs. A transaction that touches only owned objects need not take a total order with every other transaction, under the docs' rules.
Model
What has to hold
You are reading Sui's object documentation. A consensus overview that skips objects has skipped the programming model.
Falsifier
What would retire it
Which objects in the transaction are shared?
03 The mechanism
Observation
What the study says
An owned object has a single owner. A transaction on it can be certified without ordering it against unrelated owners.
Model
What has to hold
You are reading Sui's object documentation. A consensus overview that skips objects has skipped the programming model.
Falsifier
What would retire it
What prevents two transactions spending the same owned object?
04 The bound
Observation
What the study says
This note does not quote a transactions-per-second number.
Model
What has to hold
You are reading Sui's object documentation. A consensus overview that skips objects has skipped the programming model.
Falsifier
What would retire it
What prevents two transactions spending the same owned object?
03 Sequence
One action, as an operating tape
- 01An owned object has a single owner. A transaction on it can be certified without ordering it against unrelated owners.
- 02A shared object is ordered. The fast path does not apply.
- 03Move's type system is supposed to make object ownership explicit. A bug that forges an owner is a break of the model, not a fee event.
04 Load-bearing
The argument, and where a pitch drops it
What the name has to mean
The cut
Sui's Move dialect publishes objects with owners and IDs. A transaction that touches only owned objects need not take a total order with every other transaction, under the docs' rules.
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
The Sui consensus paper or overview already in the library is a different page if it does not specify the object rules.
What actually moves
The cut
A shared object is ordered. The fast path does not apply.
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
The Sui consensus paper or overview already in the library is a different page if it does not specify the object rules.
What a later deployment may change
The cut
Move's type system is supposed to make object ownership explicit. A bug that forges an owner is a break of the model, not a fee event.
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
This is not Aptos's Move. The object model differs.
05 Register
What has to be true
Model · Not re-measured
You are reading Sui's object documentation. A consensus overview that skips objects has skipped the programming model.
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
This is not Aptos's Move. The object model differs.
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
- 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
Object-centric is not 'faster Solana'. It is a claim about which transactions commute. Shared objects do not commute.
What the design proposes
- An owned object has a single owner. A transaction on it can be certified without ordering it against unrelated owners.
- A shared object is ordered. The fast path does not apply.
- Move's type system is supposed to make object ownership explicit. A bug that forges an owner is a break of the model, not a fee event.
How the mechanism is specified
- An owned object has a single owner. A transaction on it can be certified without ordering it against unrelated owners.
- A shared object is ordered. The fast path does not apply.
- Move's type system is supposed to make object ownership explicit. A bug that forges an owner is a break of the model, not a fee event.
What this page does not treat as proven
Why the desk still reads it
Sui's Move dialect publishes objects with owners and IDs. A transaction that touches only owned objects need not take a total order with every other transaction, under the docs' rules.
09 Lexicon
Terms, opened into the record
- Owned object
- An object with one owner. Unrelated owners can proceed without a global order.
- Shared object
- An object many parties can touch. It requires ordering.
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.