Layer 1 · Reviewed August 6, 2026
Sui (SUI)
The object-centric data model is the most genuinely novel Layer 1 design shipped in years, and it delivers real advantages in parallelism, safety and user experience. The token's distribution to insiders is the reason this is not a higher score.
By Dana Reyes · Analyst holds no position in SUI.

Most new Layer 1s are variations on a theme: take an account-based ledger, make consensus faster, market the throughput. Sui did something structurally different. It models everything on chain as an object with an owner and a type, rather than as entries in a global account table. A coin is an object. An NFT is an object. A liquidity position is an object. This sounds like a taxonomy exercise until you follow the consequences, which are substantial and mostly excellent.
The first consequence is parallelism that comes free rather than through heuristics. If a transaction only touches objects you own — sending a coin, transferring an NFT — the network can prove no other transaction conflicts with it and skip global consensus entirely, finalising in a few hundred milliseconds through a simpler broadcast protocol. Only transactions touching shared objects, like a DEX pool, require full consensus. Other chains achieve parallel execution by guessing at dependencies and re-running on conflict; Sui knows the dependency graph from the transaction itself. That is a cleaner solution to the same problem.
The second consequence is safety. Move, the language Sui uses, treats assets as linear resources that cannot be copied or accidentally discarded — the type system enforces conservation at compile time. Whole classes of bug that have drained hundreds of millions from Solidity contracts, from double-spend logic errors to reentrancy, are not merely discouraged but unrepresentable. Combined with formal verification tooling that is genuinely usable, this is the strongest smart-contract safety story of any high-throughput chain.
The third consequence is user experience, which Sui has exploited well. Sponsored transactions let applications pay gas for users. zkLogin lets someone create a self-custodial wallet using an existing OAuth account without ever seeing a seed phrase, with zero-knowledge proofs keeping the identity link private. Programmable transaction blocks let a single user action chain dozens of operations atomically, so complex flows feel like one tap. Storage costs are prepaid into a fund that rebates when data is deleted. These are the details of a team that has clearly thought about consumer products rather than only about benchmarks.
In production it has held up. Sui has processed very high sustained transaction volumes with sub-second finality and negligible fees, and its ecosystem now includes credible DeFi — lending, DEXs with real depth, perpetuals, native and bridged stablecoins — plus a gaming and consumer segment that is more active than most competitors'. Notably it has attracted a genuine Bitcoin-liquidity niche, with wrapped BTC and BTC-denominated DeFi becoming an unusually large share of its TVL. That is a differentiated position rather than a copy of someone else's playbook.
The team is technically formidable. The founders led the Diem and Move work at Meta, meaning they had already built this class of system once, at scale, under regulatory scrutiny, before starting again unencumbered. Engineering output has been consistently fast and consistently high quality, and the network has avoided the extended outage history that plagued the previous generation of performance chains.
Now the objection that matters. Sui's token distribution is heavily weighted toward early contributors, investors and the foundation. A large majority of supply sat with insiders at launch, circulating supply started small, and the unlock schedule has been releasing tokens continuously into the market for years — a structural, scheduled supply of sellers who acquired at prices unavailable to anyone else. Whatever one thinks of the technology, this is a distribution profile that transfers value from later buyers to earlier ones by design, and our framework penalises it consistently regardless of how good the chain is.
Decentralisation is a related concern. The validator set is professional and reasonably sized, but stake concentration is meaningful and foundation-linked delegation has been an important share of it. Governance is not yet a mature on-chain process with real authority; direction comes from the core company and foundation. Again, normal for the stage, but it means the network's neutrality is currently a matter of trust rather than structure.
The Move ecosystem tax is the last drag. Move is a better language than Solidity by most technical measures, but the developer pool is a rounding error by comparison, audited library reuse is limited, and every team building on Sui pays a hiring and tooling premium. The chain's growth therefore depends on continued ecosystem funding to subsidise that premium — which works while the treasury is large and becomes a problem if it is not.
The score is 3.8 — Promising, and the highest we assign in the new-generation L1 cohort. The object model is a real contribution rather than a marketing frame, Move materially reduces the exploit surface, the UX primitives are the best available, and execution has been excellent. It is held back from a four by an insider-heavy distribution with years of scheduled unlocks and a governance structure that still rests on the founding organisations. Superb chain; buy the technology with your eyes open about who owns the token.
What works
- — Object model delivers true parallelism and sub-second finality for owned-asset transfers
- — Move's linear resource types make entire exploit classes unrepresentable
- — zkLogin, sponsored transactions and programmable transaction blocks are best-in-class UX
What worries us
- — Insider-heavy token distribution with years of scheduled unlocks
- — Stake concentration and foundation-led direction rather than mature on-chain governance
- — Small Move developer pool raises the cost of building here