Sui Platform
What makes Sui's runtime structurally different from EVM and SVM — and where does that difference become decisive?
The object model is the foundation. Everything — coins, NFTs, devices, identities — is an object with an ID, type, owner, and data. Ownership is explicit, not inferred from a balance mapping. Parallelism follows naturally: transactions on disjoint object sets execute concurrently without coordination.
Runtime
| Concept | What It Does | Why It Matters |
|---|---|---|
| Object model | State is objects, not accounts | Ownership is structural, not convention |
| Mysticeti consensus | DAG-based BFT with ~390ms finality | Real-time agent workflows, HFT DeFi |
| Parallel execution | Object-level transaction isolation | Linear scaling with hardware |
| Storage fund | Users pay for on-chain storage; validators compensated | Sustainable economics for data-heavy apps |
| Move bytecode verifier | Checks safety invariants at publish time | Entire vulnerability classes eliminated pre-deployment |
What Goes Here
Pages in this directory document the Sui runtime internals — object model deep dives, consensus mechanics, storage architecture, and execution model. Equivalent to The EVM in the EVM section.
Context
- Sui Development — Onboarding path and what we've built
- Sui Technical — Object model, Mysticeti, agent economy primitives
- Smart Contract Comparison — Cross-platform scoring
- The EVM — EVM equivalent for comparison
Questions
Where does the object model make something trivial that other runtimes make hard — and where does it introduce friction that accounts don't have?