Sui
Objects, ambitious applications, and the cost of moving fast.
Sui is a proof-of-stake blockchain built around programmable objects. Its community connects fast execution and a broader application stack with a consumer-scale future, while outages, token releases and the Cetus recovery expose difficult questions about reliability and control.
A new chain, a different starting point
Sui opened its public mainnet on May 3, 2023. Mysten Labs created the original implementation; the Foundation supports ecosystem development. Keeping these organizations separate from the validator network helps avoid a common analytical shortcut: a company announcement can explain a product, but it is not itself evidence that every independent operator has deployed it.
The token-schedule page says approximately five percent of the eventual ten-billion-token supply circulated at launch. That makes circulating supply a central part of Sui’s history. A fixed ultimate supply and a growing tradable supply can coexist. Someone evaluating dilution needs the release schedule and actual circulation, not only the maximum printed on a market page.
Understanding the object model
Sui represents application state through objects with identities, types and ownership. Ownership determines who can use an object, while shared objects permit coordinated interaction. This gives developers a concrete way to model assets, game items and financial positions rather than treating every operation as a change to one undifferentiated global account balance.
The useful distinction is between independent work and conflicting work. Transactions that need the same shared resource still require ordering and agreement. Parallel execution is therefore a workload property, not a promise that every possible application scales without contention. For a lending market or busy exchange, the specific shared-state design matters as much as a headline transactions-per-second number.
Speed depends on the whole system
Mysticeti first reached mainnet in July 2024. The engineers’ November 2025 account of version two describes bringing transaction validation into consensus and simplifying submission through Transaction Driver. These are specific engineering changes behind the network’s speed narrative, rather than evidence that latency has disappeared.
A complete user experience includes a wallet, an RPC endpoint, consensus, execution and the application’s own services. Editorially, a useful comparison measures successful end-to-end interactions under similar load, including failures. A benchmark of one layer cannot settle whether a game, payment or trading application will feel fast on an ordinary phone.
The storage fund and the token
SUI pays network fees and supports proof-of-stake security. The original tokenomics explanation separates computational work from the burden of retaining data. Storage payments help fund future validators who may inherit data created long before they joined. This attempts to match a long-lived obligation with a long-lived funding mechanism.
Deleting eligible stored data can return part of the storage payment. Consequently, a storage-fund balance should not casually be equated with an irreversible burn of every deposited token. The stronger scarcity story needs measurement: net storage deposits, rebates, circulating releases and demand for liquid SUI. Our interpretation is that a designed token sink is an economic mechanism to investigate, not a valuation formula.
From a chain to an application stack
The Foundation’s 2025 retrospective describes Walrus storage, Seal access control and Nautilus offchain computation alongside Sui itself. Together they illustrate the ambition to give developers several building blocks for applications that cannot keep all their data or computation directly on a blockchain.
Those components should be evaluated separately. A storage layer is not automatically the same security system or token economy as the execution chain; an access-control service adds its own assumptions. The meaningful adoption question is whether applications retain paying users and remain usable when a component fails. A collection of launches establishes availability, while durable demand requires later evidence.
Cetus, outages, and difficult tradeoffs
After the 2025 Cetus exploit, a stake-weighted vote approved a narrowly specified recovery upgrade for frozen funds. The Foundation’s record says validators representing 90.9 percent of stake voted yes, with Foundation stake excluded from the vote, and describes a multisignature custody arrangement. This is evidence of an explicit governance intervention. It does not establish that the original exploit compromised Sui’s base consensus.
The January 2026 postmortem attributes a roughly six-hour stall to divergent validator consensus processing. The May postmortem describes three further halts involving gas-charging changes and randomness-state handling. Both reports say committed state was preserved. That distinction matters: avoiding conflicting finalized transactions is a safety result, while being unable to transact is still an availability failure.
How we got here.
- 2023-05-03
Public mainnet opens
The network launches, with only part of its ultimate SUI supply initially circulating.
- 2024-07
Mysticeti reaches mainnet
The later engineering retrospective dates the first deployment of the DAG-based consensus system to July.
- 2025-05
Cetus recovery vote
Validators approve a targeted intervention to recover frozen exploit proceeds.
- 2025-11
Mysticeti v2 explained
Engineers describe integrated validation and changes to transaction submission.
- 2026-01-14
Consensus processing stall
The network pauses checkpoint certification and resumes after validator upgrades.
- 2026-05-28 / 29
Three mainnet halts
The published postmortem documents distinct bugs and the risks of an interim recovery fix.
Beliefs, ambitions & unanswered questions.
These are attributed narratives, not endorsements. Open each evidence file to see the supporting record and the limits of what it establishes.
Future possibilityThe consumer blockchain thesis
Open evidence file
Fast, programmable objects could make Sui a home for everyday applications.
Where the story comes from
The Foundation’s Sui Stack retrospective links execution, storage and access control to a broader application vision.
What the record supports
- Object ownership is a concrete developer primitive; the stack includes separately documented components rather than only an announced aspiration.
What it does not prove
- Availability of infrastructure does not demonstrate mainstream retention, sustainable application revenue or superiority for every workload.
- Performance claims need a specified workload and measurement window. The 2026 halts belong in any reliability assessment.
What to watch
- Look for repeat users after incentives end, application-level failure rates, developer retention and published postmortems.
Contested interpretationThe storage-driven scarcity story
Open evidence file
Growth in stored data will make liquid SUI scarcer and reward holders.
Where the story comes from
A March 2025 r/sui discussion tied Walrus adoption to SUI scarcity and circulated numerical projections. It is a record of community enthusiasm, not an audited economic model.
What the record supports
- The original tokenomics explanation describes a storage-funding mechanism; the storage-fee guide describes deposits and partial deletion rebates.
What it does not prove
- A hypothetical storage forecast does not establish actual deposits, net circulating supply or a future market price.
- Walrus and Sui activity must not be conflated; the release schedule and withdrawal mechanics belong in the same calculation.
What to watch
- Compare measured storage-fund changes with rebates and newly circulating tokens, then test whether observed demand persists.
Contested interpretationRecovery as resilience—or discretionary control
Open evidence file
The Cetus response shows either a community protecting users or a network willing to override ownership.
Where the story comes from
The May 2025 recovery proposal and contemporary r/sui responses preserve both the intervention and disagreement about its meaning.
What the record supports
- The official plan explicitly authorized two recovery transactions without the attacker’s signatures and used a stake-weighted vote.
What it does not prove
- A narrowly scoped intervention is not proof that arbitrary balances are routinely confiscated.
- A favorable vote also does not erase the precedent. Censorship resistance, user restitution and validator discretion are different values.
What to watch
- Read the actual upgrade scope, validator voting concentration and published rules for any future exceptional intervention.
The source library.
Primary documents explain mechanics and decisions. Community records show what participants believed. Dates below indicate when these links were reviewed; external pages may change.
- Object model ↗Sui documentation · primary · Reviewed 2026-09-22
- SUI token supply and circulation ↗Sui Foundation · primary · Reviewed 2026-09-22
- Announcing Sui Tokenomics ↗Sui Foundation · primary · Reviewed 2026-09-22
- All about storage fees ↗Sui Foundation · primary · Reviewed 2026-09-22
- Mysticeti v2 ↗Mysten Labs engineers · primary · Reviewed 2026-09-22
- 2025: how the Sui Stack came together ↗Sui Foundation · primary · Reviewed 2026-09-22
- Cetus recovery: the onchain vote ↗Sui Foundation · primary · Reviewed 2026-09-22
- January 2026 mainnet stall resolution ↗Sui Foundation · primary · Reviewed 2026-09-22
- May 2026 mainnet halts postmortem ↗Sui Foundation · primary · Reviewed 2026-09-22
- SUI + Walrus = deflation: community discussion ↗r/sui participants · community · Reviewed 2026-09-22
- Cetus update and community responses, May 23, 2025 ↗r/sui participants · community · Reviewed 2026-09-22