Sui Standards
What happens when the language IS the standard — and there's no separate ERC to implement?
EVM standardizes the interface (ERC-20 defines the shape, anyone implements). Solana standardizes the program (SPL Token is one shared implementation). Sui standardizes at the language level — every object with key is already uniquely identified, owned, and transferable. There's no separate NFT standard because the object model already handles it.
Core Standards
| Standard | EVM Equivalent | What It Does |
|---|---|---|
sui::coin | ERC-20 | Typed fungible tokens. Coin is an object wrapping a Balance. |
Object with key | ERC-721 | Any object with key ability is an NFT by default. |
| Composable objects | ERC-1155 | Objects can own other objects. No special standard needed. |
| PTBs | Multicall + EIP-7702 | Up to 1,024 operations with data flow between them. Atomic. |
| zkLogin | ERC-4337 | Protocol-level account abstraction. OAuth → Sui address via ZKP. |
| Capability pattern | Role-based modifiers | Compiler-enforced access control via owned capability objects. |
Our Implementations
From the Move packages:
| Package | Standard Pattern | Lines |
|---|---|---|
| identity | Capability (AdminCap) + attestation objects | 327 |
| link | Owned objects with genealogy + shared attribution rules | 459 |
| mandate | Shared objects for cross-party AP2 commerce | 253 |
| device_registry | Typed objects with state machine lifecycle | 402 |
What Goes Here
Pages in this directory document Sui-native standards — coin types, object patterns, PTB recipes, zkLogin integration. Equivalent to ERC Standards in the EVM section.
Context
- Sui Development — Full onboarding and what we've built
- ERC Standards — EVM equivalent for comparison
- Smart Contract Comparison — Standards War — Governance models compared
- SIP Repository — Sui improvement proposals
Questions
If the language makes standards unnecessary, what happens when the language itself needs to evolve faster than deployed contracts can adapt?