Objects All
The Way Down
This is not an article about Sui's object model.
This article is an object model. Every section is an object. Interact with them.
scroll to inspect objects ▊
The Foundation
Is Wrong
Let me be blunt about something the crypto world does not love hearing: the chains we have been building on were designed for a reality that has already passed us by. Ethereum showed up in 2013 with an account model — essentially a giant shared spreadsheet where your tokens are just numbers next to your address, stored inside someone else's smart contract. It was revolutionary for its time. But time has moved on.
The problem is not that Ethereum's model does not work. It does. The problem is how it works. Every transaction, no matter how trivial, stands in line behind every other transaction touching the same state. One viral NFT mint can choke the entire network. Gas fees spike to absurd levels. Confirmations slow to a crawl. You are looking at a single-lane highway pretending to be infrastructure for a global financial system.
This is not a new complaint. But what is new is that a team of five engineers — Evan Cheng, Sam Blackshear, Adeniyi Abiodun, George Danezis, and Kostas Chalkias — actually went back to the drawing board. These are the same people who built the Move programming language and the Diem blockchain at Meta. When regulators killed Meta's crypto ambitions, they did not retire. They founded Mysten Labs and spent two years asking a dangerous question: what if we threw out the account model entirely and started from first principles?
Sui went live on mainnet in May 2023. The pitch was deceptively simple: stop treating digital assets like rows in a database. Start treating them like what they actually are — independent, ownable things with their own identity and rules. That single architectural decision changes everything that follows.
Every Asset Gets
Its Own Life
Here is the thing that clicked for me when I first dug into Sui: on Ethereum, if you own an NFT, it does not really live with you. It is a line item inside a shared smart contract. A global ledger says "token #847 belongs to address 0x7b," and to do anything with that token, the whole contract has to be read, verified, and updated. Your transaction waits behind everyone else touching that same contract. Every user of every dApp backed by that contract is in the same queue.
Sui inverts this completely. Your NFT is not an entry anywhere. It is a standalone object — with its own globally unique ID, its own ownership metadata, its own access rules. Think of the difference between renting a storage locker in a massive warehouse where every locker shares one entrance, versus actually holding the thing in your hands and walking wherever you want.
This is where parallel execution becomes inevitable rather than aspirational. Because every object is self-contained, the network can instantly determine which transactions are independent. Two people trading different tokens? Those execute at the same time, on different validators, with zero contention. It is not the hand-wavy "we will shard it eventually" kind of parallel — it is baked into the data model from day one.
Simple operations — sending tokens, minting an NFT, transferring ownership — do not even need full consensus. They take a "fast path" where a handful of validators confirm ownership, sign off, and finalize. Sub-second. No gas war. No MEV sandwich attacks on your transfer. Shared objects like DEX liquidity pools go through Sui's Mysticeti v2 consensus, which still settles in approximately 390 milliseconds. For context, Ethereum's finality takes around 15 minutes. Solana's takes 2-3 seconds.
Then there is Move — Sui's programming language, originally created by Sam Blackshear for Meta's Diem project. Move treats digital assets as "resources": first-class types that cannot be copied, accidentally destroyed, or double-spent. The compiler will not let you. Five of the OWASP Top 10 smart contract vulnerabilities are structurally impossible in Move. Three more are partially mitigated. Security is not bolted on after the fact — it lives in the grammar of the language itself.
Objects Are
Composable
Here is something most people miss about Sui: it is not just that objects execute in parallel. It is that you can compose them. On Sui, a single transaction can touch multiple objects atomically through what is called a Programmable Transaction Block (PTB). You can split a coin, swap it on a DEX, use the proceeds to mint an NFT, and transfer that NFT to a friend — all in one atomic operation. If any step fails, everything reverts cleanly. No multi-step approvals. No partial failures. No stuck intermediate states.
On Ethereum, that same workflow requires four separate transactions, each with its own gas fee, each vulnerable to front-running, each capable of leaving you in a broken intermediate state if one fails halfway through. PTBs are not just a convenience feature — they are a fundamentally different programming model that makes complex operations safer and cheaper.
Try it yourself. Click objects to add them to the transaction block below and watch the code compose:
Not Just a Chain.
A Complete Stack.
Here is what separates Sui from every other Layer 1 project I have followed: they did not just ship a blockchain and hand developers a "good luck." Throughout 2025, Mysten Labs and the Sui ecosystem assembled every missing piece of decentralized infrastructure into one vertically integrated platform where every layer speaks Move natively. No other blockchain has pulled this off — not Ethereum, not Solana, not anyone. Click each layer to inspect:
The base layer. Object-centric data model with parallel execution. Mysticeti v2 consensus achieves ~390ms finality. Move language prevents five of the top ten smart contract vulnerabilities at the compiler level. Peak throughput: 120,000+ TPS.
Decentralized blob storage launched March 2025. Data is cryptographically verifiable, content-addressed, and programmable through Move. Backed by a16z, Standard Crypto, Franklin Templeton. Crossed 1 petabyte within months.
Programmable access control with threshold encryption. Only NFT holders can see a file? Data self-destructs after 30 days? All enforceable on-chain with no single point of failure.
Off-chain computation inside TEE enclaves producing cryptographic proofs Sui can verify. An AI model runs inference and proves on-chain it used the correct model with correct inputs. This makes autonomous AI agents viable.
A fully on-chain central limit order book. Institutional-grade matching engine where every order and fill is transparent and verifiable. Combined with sub-second finality, enables real-time trading impossible on other L1s.
2026:
Compounding Momentum
The building phase is largely done. What 2026 is about is proving that all these pieces compound — that the stack generates a flywheel of real, sticky adoption rather than speculative hype cycles. And honestly, the early signals are stronger than anything I have seen from a non-Ethereum L1:
Objects All
The Way Down
What makes me genuinely bullish — and I do not throw that word around loosely — is that this growth is not speculative. It is not token price going up because someone tweeted. It is developers shipping real products on infrastructure that works. They ran 1.16 billion programmable transaction blocks on Sui in 2025 alone. Developer growth hit 219% year-over-year, outpacing Solana's 83% by a factor of 2.6x. Over a petabyte of decentralized storage is live and being used in production. These are not testnet benchmarks. These are load-bearing numbers.
The question used to be "can Sui's technology actually work at scale?" That question has been answered emphatically. The question now is whether the ecosystem converts this architectural advantage into the kind of compounding, sticky adoption that creates a lasting network effect. And 2026 — with privacy features going live, institutional products launching, AI infrastructure maturing, and Bitcoin becoming productive on Sui — looks like the year we find out.
If the answer is yes, the implications extend far beyond one chain outperforming another. It means the core abstraction we use for the decentralized web permanently shifts: from accounts to objects, from sequential to parallel, from patching old systems to building ones that were designed correctly from the beginning.
And if that sounds familiar, it is because you just experienced it. Every section you read was an object — with a unique ID, an owner, metadata, and dependencies. You raced parallel execution against sequential. You composed a Programmable Transaction Block from independent objects. The medium was the message.
Objects all the way down.