Layer 1 blockchain
Sui ticker SUI
Summary
Delegated proof-of-stake layer 1. SUI holders delegate stake to validators for roughly 24-hour epochs, and decisions need validators holding more than 2/3 of voting power. Validators run Mysticeti, which builds a directed acyclic graph of blocks proposed in parallel; Sui's docs say it needs only three rounds of messages to commit, while Sui's November 2025 Mysticeti v2 post put the median for transactions at four rounds, with three as a goal. Executed transaction effects are certified by a quorum and batched into checkpoints signed by more than 2/3 of the committee. From node v1.60 (November 2025) Mysticeti v2 folds transaction validation into consensus. The documented penalty for a poorly performing validator is a cut to its rewards through peer scoring; slashing of staked principal is not described. 12359103738
Design
- System
- Layer 1 blockchainPermissionless proof-of-stake base layer. Consensus orders blocks that many validators propose in parallel as a directed acyclic graph (Mysticeti) rather than one chain of blocks, and the network's hash-linked history is a sequence of certified checkpoints, so block-interval metrics apply only loosely.
- Settlement family
- Its own design
- Scarce resource
- Stake (proof of stake)
- State model
- Other
- Finality
- Other
- Who makes blocks
- Every validator in the active committee can propose consensus blocks in parallel, and Mysticeti votes on and certifies leader blocks in parallel. A candidate needs at least 3 units of voting power to join (SIP-39); Sui's network page lists more than 100 mainnet validators plus 2 operated by Mysten Labs.
- Fork choice
- No longest-chain or heaviest-chain rule. A transaction is final once validators with more than 2/3 of voting power certify its effects, and a certified checkpoint is permanent history. When validators derived different consensus output in January 2026, the network halted instead of forking, and Sui reports that no certified transaction was rolled back.
Qualifications
- Block time · Partial. There is no single fixed block interval: consensus blocks form a graph proposed in parallel, and users see certified checkpoints, so block-interval measures apply only approximately.
- State model · Partial. Object-centric ledger in which every object has an ID, a version and an owner. Since May 2026 each address can also hold one protocol-maintained balance per coin type alongside coin objects, so neither the account label nor the UTXO label fits fully.
- Finality · Applies. Deterministic committee finality: a transaction is final once validators with more than 2/3 of voting power certify its effects, typically 400 to 700 ms end to end according to Sui's docs. It is not recorded as economic finality because the documented penalty reduces rewards rather than staked principal.
- Tps · Contested. Sui's own publications give different benchmark figures for its consensus engine; they appear only as classified benchmark claims, and no observed mainnet window was recorded.
- Move language peers · Not applicable. Sui's objects, ownership types and address balances are specific to Sui, so using the Move language does not by itself describe how Sui's ledger works.
- Settlement family · Partial. Recorded as other: Sui settles on its own proof-of-stake chain, where validators run Mysticeti consensus, certify transaction effects and sign checkpoints over an object-centric Move ledger; nothing settles to another chain. None of the named settlement families describes this.
Tradeoffs
- Emphasizes
- Scalability and Security Contested
- Gives up
- Operational decentralization and liveness margin. Sui's suggested full node has 128 GB of RAM and a 4 TB NVMe drive, validators are asked for 24 physical cores and 1 Gbps, and the active set is around one hundred validators. Software bugs halted the network for about six hours in January 2026 and three more times on 28 and 29 May 2026.Security here means safety while more than 2/3 of stake is honest: Sui's incident reports say the halts kept finalized history intact. Whether about one hundred high-specification validators is adequately decentralized is disputed. The 2025 Cetus recovery, where a stake-weighted validator vote approved a protocol upgrade that moved specific frozen funds, is recorded here as a fact about governance reach, not as a verdict.
- Full node at home
- Demanding 678Sui suggests 8 physical cores (16 vCPUs), 128 GB RAM and a 4 TB NVMe drive for a full node and recommends starting from a snapshot rather than syncing from genesis. Its storage page, with mainnet figures as of November 2025, gives about 2.5 TB for a pruned full node and 16 TB for an unpruned node keeping full history, which grew by about 10 to 40 GB per day depending on network load. Validators are listed at 24 physical cores, 128 GB RAM, 4 TB NVMe and 1 Gbps.
- Throughput claims
- Lab benchmark: 400,000 tx/s 2Controlled benchmark; not observed network behavior.Throughput reached before consensus latency passed 1 second in a 50-node benchmark; test date not stated.Not stated on the documentation page.Measures the Mysticeti consensus engine in a benchmark, not observed Sui mainnet load or end-to-end execution. The same page gives 300,000 for a 10-node test and a sustained 200,000 at about 0.5 seconds of commit latency; hardware, transaction mix and network conditions are not stated. Ignores state growth, contention on shared objects and propagation to full nodes; not comparable with another chain's figure.
- Lab benchmark: 100,000 tx/s 40Controlled benchmark; not observed network behavior.Throughput at about 1 second of latency in a wide-area-network test reported by Sui in April 2024.An earlier Sui figure for the same consensus design that differs from the later documentation benchmark, which shows how strongly results depend on test setup. Test hardware and transaction mix are not described in the post; this is not observed mainnet load.
Scaling layers
No scaling layer recorded in this profile.
Capabilities
| Capability | How it is provided | Notes and sources |
|---|---|---|
| Account abstraction | Structured assessment pending | Not yet assessed for any chain. |
| Atomic swaps | Unknown | Not yet assessed under the current definitions; the reviewed evidence is building blocks. A programmable transaction runs up to 1,024 commands all-or-nothing, and Sui's docs publish a sample escrow contract in which two parties swap locked objects without trusting each other; no live mainnet swap tool built on it is cited. No protocol-level cross-chain hash-time-locked swap was verified. 1115 |
| Authenticated data publication | Core-team softwareLimited scope | Walrus, a storage network coordinated through Sui, stores public blobs whose IDs are derived from their content and records on Sui an availability certificate signed by storage nodes holding 2/3 of shards, so a reader can fetch a blob from those nodes and check it against its ID. Mysten Labs publishes the implementation (the MystenLabs/walrus repository the Walrus docs link to); the storage nodes' operators were not reviewed. Limited: a blob cannot be changed without changing its ID, and no way to discover updates is described. 18 |
| Light clients | Built into the protocolLimited scope | Consensus produces what a light client checks: the last checkpoint of each epoch names the next committee and its keys, so a client holding the genesis checkpoint can verify later checkpoints and, through them, transactions, events and objects. Mysten's own repository ships a command-line light client that does this. Limited: it fetches data from a full node or archive and must be synced regularly, and wallet adoption was not reviewed. 516 |
| Native staking or delegation | Structured assessment pending | Not yet assessed for any chain. |
| On-chain governance | Structured assessment pending | Not yet assessed for any chain. |
| Parallel execution | Structured assessment pending | Not yet assessed for any chain. |
| Payment or state channels | Unknown | No payment or state channel network anchored to Sui was reviewed. |
| Programmable spending | Native (protocol or core-team software) Earlier definition | Move contracts govern objects; one transaction can chain up to 1,024 commands; native multisig can mix Ed25519, secp256k1 and secp256r1 keys; zkLogin lets an OAuth login plus a zero-knowledge proof authorize an address, with the verifying key built into validator software. 111213 |
| Protocol-verified messaging | Structured assessment pending | Not yet assessed for any chain. |
| Reversible transfers or recovery | Unknown | Not yet assessed under the current definitions; no way for a sender to cancel or reclaim a payment was reviewed. Native multisig (up to 10 weighted keys) can include a backup signer, which Sui's zkLogin docs recommend for recovery; that is a plain multisig threshold, which the current definition does not count as a recovery path. Issuers of regulated coins can block addresses from sending the coin, but the docs describe no seizure; the 2025 Cetus fund recovery was a one-off validator-approved upgrade, not a user feature. 12131436 |
| Rollups | Unknown | No rollup settling to Sui was found in reviewed sources; absence was not exhaustively verified. |
| Shielded transfers | Structured assessment pending | Not yet assessed for any chain. |
| Signed partial offers | Unknown | Not yet assessed under this row's current definition. |
Reading these values
- How this feature is provided
- Built into the protocol, core-team software or independent software says where a feature lives and who can change it. These are implementation layers, not quality: core-team software is not closer to the protocol than independent software.
- Structured assessment pending
- The shared review has not assessed this feature for any chain yet (Account abstraction, Native staking or delegation, On-chain governance, Parallel execution, Protocol-verified messaging and Shielded transfers). That does not mean it is absent, and a chain’s profile may already describe it.
- Unknown
- The review has not established this for this chain under the current definition; the note beside it says why. Unknown is not absent and not a low score. A feature reads “Not present” only when a source shows it is absent.
- Earlier definition
- Payment or state channels, Programmable spending and Rollups keep the earlier definition until the next fact-check. There, “Native” does not separate the protocol from core-team software, “Ecosystem software” does not say who publishes it, and “Partial” does not say which layer.
- Reading across rows
- The list of capabilities is incomplete. Do not read these rows as a chain leading or lagging overall.
Ecosystem & custody
| Product type | Status | Notes and sources |
|---|---|---|
| Automated market makers | Established in the ecosystemCetus (concentrated-liquidity AMM), DeepBook (order book, not an AMM) | Cetus describes itself as a concentrated-liquidity exchange built on Sui. DeepBook v3 runs order-book markets as shared-object pools and is listed for context only. Cetus was exploited in May 2025, and recovering the frozen funds needed a validator vote on a protocol upgrade. 192036 |
| Issuer-native stablecoins | Established in the ecosystemUSDC (Circle), USDsui (issued through Bridge), AUSD (Agora), FDUSD (First Digital) | Circle lists a native USDC coin type on Sui. Sui's gasless-transfer allowlist names USDC, USDsui, suiUSDe, USDY, FDUSD, AUSD and USDB. USDsui was announced in November 2025 as a Sui-branded dollar issued through Bridge's Open Issuance platform. Tether's supported-protocol list does not include Sui, so USDT on Sui would be a bridged representation. 17212324 |
| Algorithmic stablecoins | Unknown | No algorithmic stablecoin with material usage was verified. suiUSDe, issued with Ethena, is a synthetic dollar backed by digital assets and matching short futures positions; that is hedge-backed rather than algorithmic, with different risks from reserve-backed coins. 25 |
| Bridges | Native to the protocolSui Bridge (Ethereum), Circle CCTP, legacy version (USDC), Wormhole (wrapped token transfers) | Sui Bridge is a Sui framework package operated by a committee of Sui validators; it launched on mainnet in September 2024 for ETH and WETH between Ethereum and Sui. Circle lists Sui only under the legacy first version of its burn-and-mint transfer protocol. Wormhole lists Sui for wrapped token transfers. Risk: Sui Bridge rests on the honesty of the signing validator committee and on its Move and Ethereum contracts; per-route hourly limits in US-dollar terms cap losses but do not remove them. Wormhole-wrapped tokens depend on Wormhole's own security model and on the origin chain, and Circle marks Sui's burn-and-mint route as legacy. 22262728 |
| Block explorers | Established in the ecosystemSuiscan, SuiVision, Polymedia Explorer, OKLink | Sui's tooling page lists these explorers; Suiscan links to Blockberry and SuiVision to BlockVision. Listing is not a quality or completeness check, and explorer data is provider-indexed. 29 |
| Hardware wallets | Established in the ecosystemLedger | See custody rows: Ledger maintains a Sui device app and Sui code in Ledger Wallet, although Ledger's Sui page still describes a third-party wallet path; Trezor states that it does not support Sui. A Sui-specific device, Suiball by Citadel, was announced for pre-order in October 2025 and was not verified as shipping. 30313435 |
Hardware-wallet custody
| Device maker | Status | What users can and cannot do |
|---|---|---|
| Ledger | Native supportSame as native: Unknown | Can: Hold Sui keys on Ledger Nano S Plus, Nano X, Flex or Stax with Ledger's Sui device app Can: Send and receive SUI and Sui tokens in Ledger Wallet, announced by the Sui Foundation in April 2025 and backed by a Sui module in Ledger's wallet code Can: Sign Sui transactions from a compatible third-party Sui wallet, the path Ledger's Sui page describesLedger's own Sui page, last modified in October 2024, still tells users to connect a third-party Sui wallet, which predates the April 2025 integration announcement. Ledger's open-source wallet code contains Sui staking and unstaking logic, but staking and swaps inside Ledger Wallet were not confirmed on a Ledger page. 30313233 |
| Trezor | None foundSame as native: No | Cannot: Manage SUI in Trezor Suite Cannot: Use a Trezor for Sui through a path Trezor supportsTrezor's Sui page states that Trezor does not currently support Sui. 34 |
Public data
iKnow Blockchain has no public-data lookups for Sui yet. This is a limit of the service, not a statement about the network.
| Lookup | Status | What it covers and its limits |
|---|---|---|
| Address or account | Not available yet | Public-data lookups for this chain are not built yet. |
| Tokens and assets | Not available yet | Public-data lookups for this chain are not built yet. |
| NFTs | Not available yet | Public-data lookups for this chain are not built yet. |
| Transactions | Not available yet | Public-data lookups for this chain are not built yet. |
Sourced developments
Developments: Review overdue Reviewed Sep 27, 2026; next review was due Oct 7, 2026, 12:00 UTC.
Publication date · newest first
-
Node release mainnet-v1.80.1 carries Sui protocol version 137
Mysten Labs published node release mainnet-v1.80.1 on 23 September 2026 with protocol version 137. Its protocol changes make Ristretto255 range proof checks cheaper and raise their size cap from 512 to 1,024 (commitments times range bit length), charge gas for loading a Move constant by the size of its value rather than its encoded length, accept on every network a transaction expiry option that limits which validators may propose a transaction, and reject malformed transactions earlier during signing. The release also adds an allowances feature, but a change merged into the v1.80 release branch keeps allowances switched off on mainnet at version 137.
- Implementation:protocol version 137 changes included in the v1.80 release branch
- Release:mainnet-v1.80.1 released 2026-09-23; testnet-v1.80.1 released 2026-09-22
- Activation:mainnet activation epoch not verified; allowances kept off on mainnet at version 137
Sources: MystenLabs/sui repository — mainnet-v1.80.1 (external site) · MystenLabs/sui repository — MystenLabs/sui releases (external site) · MystenLabs/sui repository — [cherry-pick][v1.80] Cherry-pick #28033: protocol-config: keep allowances off on mainnet in version 137 (external site) · MystenLabs/sui repository — protocol-config: enable allowances on mainnet in v138 (external site) · Sui Documentation — Protocol upgrades (external site)
-
Three Sui mainnet halts on 28 and 29 May 2026
Sui mainnet stopped three times over two days. Two halts came from a gas-charging bug involving address balances introduced in release 1.72, which caused an arithmetic underflow during settlement; the third came from a latent bug in how validators keep randomness state across restarts. Sui reports that no user funds were at risk and no committed transaction was reverted.
- Implementation:three fixes implemented
- Release:emergency node releases shipped on 28 and 29 May 2026
- Activation:network resumed after each halt
Sources: Sui Foundation blog — Sui mainnet halts resolved after major upgrade (external site) · MystenLabs/sui repository — MystenLabs/sui releases (external site)
-
Address balances and gasless stablecoin transfers shipped for Sui mainnet
Node release mainnet-v1.72.2 added address balances, a per-address balance for each coin type alongside coin objects, and gasless transfers for seven allowlisted stablecoins (USDC, USDsui, suiUSDe, USDY, FDUSD, AUSD and USDB) with a 0.01 minimum. The Sui Foundation announced the transfers as rolling out on mainnet the same day.
- Proposal:SIP-58 (address balances)
- Implementation:implemented in node v1.72.2
- Release:mainnet-v1.72.2 released 2026-05-20
- Activation:announced as rolling out on mainnet on 2026-05-20; exact activation epoch not verified
Sources: MystenLabs/sui repository — mainnet-v1.72.2 (external site) · Sui Foundation blog — Sui launches gasless stablecoin transfers (external site) · Sui Documentation — Gasless stablecoin transfers (external site) · Sui Documentation — Address balances (external site)
-
Sui is retiring its JSON-RPC interface in favour of gRPC and GraphQL RPC
On 24 March 2026 Sui announced that its newer data interfaces (gRPC, GraphQL RPC and an archival store) were ready for production use and that JSON-RPC would be switched off on 31 July 2026. Sui's migration guide says JSON-RPC was disabled on the Sui Foundation's mainnet full nodes in the week of 27 July 2026. It gives target dates for the later steps: the Foundation stops publishing JSON-RPC snapshots at the end of August, the automatic fallback to the archival service is cut at the end of September, and JSON-RPC is removed from full nodes, code included, in mid-October 2026. A change removing the JSON-RPC service from the full node was merged on 25 September 2026.
- Proposal:deprecation announced on the Sui blog on 2026-03-24
- Implementation:JSON-RPC service removal merged into the main branch on 2026-09-25
- Release:removal not in a mainnet release as of 2026-09-27; the latest was mainnet-v1.80.1 (2026-09-23)
- Activation:disabled on Sui Foundation mainnet full nodes from the week of 27 July 2026; full decommission planned for mid-October 2026
Sources: Sui Documentation — JSON-RPC Migration Guide (external site) · Sui Foundation blog — GraphQL and Archival Store Complete the Sui Data Stack (external site) · MystenLabs/sui repository — fullnode: remove jsonrpc (external site) · MystenLabs/sui repository — MystenLabs/sui releases (external site)
-
Sui mainnet stalled for about six hours after a consensus bug
On 14 January 2026 an edge-case bug in consensus commit logic led validators to derive different commit outputs, so checkpoints could not be certified and the network halted for about six hours of user-visible disruption. Sui reports that no certified state fork occurred, no certified transaction was rolled back and no funds were lost; a fix was rolled out through canary validators and then the full set.
- Implementation:fix implemented to purge incorrect consensus data
- Release:fix deployed to canary validators, then to the validator set
- Activation:checkpoint certification resumed once a quorum signed the same checkpoint digest
Source: Sui Foundation blog — Sui mainnet network stall resolution (external site)
-
Mysticeti v2 and the Transaction Driver became Sui's default transaction path
Sui announced Mysticeti v2, which folds transaction validation into consensus, together with a Transaction Driver that submits each transaction to one validator chosen from latency history instead of to all of them; validators now sign transaction validity in batches as part of signing their consensus blocks. Node release mainnet-v1.60.1 (protocol version 101), published on 10 November 2025, made both the default. Sui reported lower latency from its own full nodes afterwards.
- Implementation:implemented in node v1.60
- Release:mainnet-v1.60.1 released 2025-11-10
- Activation:default transaction path from v1.60 according to the release notes; rollout across individual validators not independently observed
Sources: Sui Foundation blog — Mysticeti v2 (external site) · MystenLabs/sui repository — mainnet-v1.60.1 (external site)
Topics your AI can explain
Your AI can explain these topics for Sui through the connection, with sources.
Known gaps
What this profile's review did not establish:
- The validator count comes from Sui's network page (more than 100 plus 2 run by Mysten Labs); the current stake distribution and how few validators together hold 2/3 of stake were not measured.
- Whether transactions touching only owned objects still skip consensus ordering is unclear: the transaction lifecycle page says every transaction is sequenced by Mysticeti, while the shared-object page and the Mysticeti v2 post describe a faster path for owned objects.
- Slashing of staked principal is not described in the reviewed docs; only reward reduction through peer scoring was verified.
- Ledger is recorded as native from Ledger's Sui device app, the Sui module in Ledger's wallet code and the April 2025 announcement, but Ledger's own Sui page still describes a third-party wallet path; staking in Ledger Wallet was not confirmed.
- Sui Bridge's signature threshold, current per-route limit values and full asset list were not found in the reviewed pages.
- No payment channel, state channel or rollup anchored to Sui was reviewed; the scaling layer list is empty rather than confirmed empty.
- No algorithmic stablecoin with material usage was verified. Sui's gasless-transfer page attributes USDB to Bucket Protocol, but its backing and design were not reviewed.
- Walrus is assessed here for authenticated data publication; its storage-node set, token economics and retention guarantees were not reviewed.
- SuiVision returned HTTP 403 and was not fetched directly; it is listed from Sui's tooling page.
- Adoption of the command-line light client by wallets or bridges was not reviewed.
- Throughput figures are vendor benchmarks of the consensus engine only; no observed mainnet throughput window was recorded.
- Hardware figures are Sui's suggested minimums; the real resource use of a pruned full node on current mainnet was not measured.
Sources
Oldest dated source check: Source checked Sep 27, 2026 Next check due Oct 27, 2026.
- Tokenomics (external site)
- Consensus (external site)
- Transaction Lifecycle (external site)
- Security (external site)
- Checkpoint Verification (external site)
- Storage (external site)
- Sui Full Node Configuration (external site)
- Validator Deployment and Configuration (external site)
- Validator Node Rewards (external site)
- Network Info (external site)
- Programmable Transaction Blocks (external site)
- Multisig (external site)
- zkLogin (external site)
- Regulated Coins (external site)
- Trustless Swap (escrow example) (external site)
- sui-light-client README (external site)
- Gasless Stablecoin Transfers (external site)
- Core concepts (external site)
- Cetus (external site)
- DeepBook v3 design (external site)
- USDC contract addresses (external site)
- CCTP supported blockchains (external site)
- Supported protocols (external site)
- Sui unveils USDsui native stablecoin (external site)
- suiUSDe announcement (external site)
- Sui Bridge launches on mainnet (external site)
- Module sui_bridge::limiter (external site)
- Wrapped Token Transfers supported networks (external site)
- Tooling (external site)
- Sui Wallet (external site)
- app-sui (Ledger device app for Sui) (external site)
- ledger-live coin-sui module (external site)
- Ledger Live wallet self-custody for SUI (external site)
- Sui wallet (external site)
- Citadel Suiball hardware wallet (external site)
- Cetus incident response: onchain community vote (external site)
- Mysticeti v2 (external site)
- Sui mainnet network stall resolution (external site)
- Sui mainnet halts resolved after major upgrade (external site)
- Mysticeti consensus reduces latency (external site)
Report an error
Found something wrong or out of date? Reporting is free, and every chain goes through the same process. Published corrections appear in the public log.
Funding disclosure
Funding disclosures appear here when an upkeep arrangement exists, in the form “Upkeep funded by [name]; verdicts unaffected.” The funder ledger has not been published yet. Neutrality & funding