Exchange Ranking
Top Exchanges
24h Volume Ranking
Popularity Ranking
Exchange BTC Balance
Proof of Reserves
Decentralized Exchanges
Funding Rate
Funding Heatmap
Liquidation Data
Max Pain
Long/Short Ratio
Whale L/S Ratio
Binance/Okex/Huobi L/S
Bitfinex Margin L/S
ETF Tracker
Solana ETF
XRP ETF
Hong Kong ETF
Bitcoin Treasuries
Crypto Reversal
Ethereum Reserves
HyperLiquid Wallet Analysis
Hyperliquid Whale Watch
Large Transactions
On-chain Movement
Bitcoin ROI
Stablecoin Market Cap
Options Analysis
News
Articles
Economic Calendar
Features
Wallet
Contract Calculator
Security
Collections
Watchlist
Following
SUI How Sui's object model changes transaction pipelines
Most blockchains place every transaction in the same pipeline: the validator first agrees on a global ordering and then executes it. Sui adopted a different approach.
Sui, built by Mysten Labs and launched on the main network in May 2023, treats every asset (from tokens to NFTs to smart contract packages) as a separate object with a unique ID. An object can be owned by a single address, shared by multiple users, or marked immutable so that no one can change it.
This ownership tag is more than just a metadata tag. Sui classifies each object based on who can modify it, and this classification directly determines how transactions are processed.
Transactions involving only address ownership or immutable objects bypass consensus completely. The object owner signs the transaction, the verifier verifies the signature and object version, and finality is almost instantaneous. This fast path takes about 400 milliseconds on average and does not require global consensus. The practical meaning is simple: if only you can touch a given object, there is no competition, so the sorting step is skipped.
Scenarios where consensus still applies
Not every transaction can follow the fast path. Shared objects (such as a DEX liquidity pool where multiple users interact at the same time) require consensus ordering through Sui's Mysticeti protocol. Finality is still fast, about 480 milliseconds, but these transactions require serialization. A frequently used pool effectively becomes a queue, and the network sorts competing requests and executes them in order. If two users happen to submit exchange transactions for the same pool at the same time, the network will first sort the two transactions, execute the first transaction, recalculate the pool state, and then execute the second transaction against the updated state. Sequencing ensures that conflicts cannot occur.
Unlike traditional blockchain mandatory global transaction ordering, Sui introduces a causal ordering model. Verifiers can process unrelated transactions independently, and the network expands linearly as additional computing resources increase. Sui's dual consensus architecture further enhances this: Byzantine consensus broadcasts are used for simple transactions and the BFT protocol Mysticeti is used for complex shared object interactions.
In general, smart contract developers should prioritize owned objects over shared objects when reasonable: transactions involving only owned objects can completely bypass consensus ordering, while transactions involving shared objects require ordering and lead to throughput bottlenecks. Sui's guiding principle accordingly is as follows: Single-writer, delay-sensitive designs rely on owning objects, while any multi-party design incurs sequencing costs.
