Sui and Aptos · Move L1 ecosystem

Wiki route

This entry sits under systems index. Read it against DAG-BFT vs chain-BFT for the consensus framing, BFT validator economics for token / staking dynamics, and threshold BFT for the implementation-language context.

Key facts

Sui and Aptos are post-Diem (formerly Libra) L1 chains, both spawned from the 2019-2022 Meta-led Diem / Novi project that introduced the Move programming language
Sui (Mysten Labs founders) launched mainnet May 2023; emphasizes object-centric model + Narwhal / Bullshark DAG-BFT consensus
Aptos (Aptos Labs founders) launched mainnet October 2022; emphasizes AptosBFT (HotStuff-derived) chain-BFT + BlockSTM parallel execution
Move language features: resource-oriented (assets are linear types — cannot be copied / dropped), formal-verification friendly, capability-based access
Financial use cases: Sui-native USDC (CCTP V2 supported), Aptos-native USDC, RWA experiments, agent-payment infrastructure

Move language origin and design

Property	Move	EVM Solidity comparison
Asset model	Resources — linear types; assets are first-class non-copyable values	ERC-20 / NFT balance tables
Storage	Per-account / per-object; explicit ownership	Contract-storage slots
Formal verification	Move Prover integrated	None (external tooling required)
Reentrancy	Largely structurally prevented by resource model	Major historical attack surface
Capability access	First-class	Modifiers / roles patterns

Move emerged from the Diem / Libra project; when Meta wound down the consortium (2022), the two main engineering groups split:

Mysten Labs → built Sui
Aptos Labs → built Aptos

Both inherited Move but evolved it differently: Sui Move has object-centric storage (objects with IDs as the primary model) while Aptos Move stayed closer to original Diem Move with account-centric resources.

Sui vs Aptos architectural divergence

Dimension	Sui	Aptos
Storage model	Object-centric (each on-chain entity is an object with owner)	Account / resource (account holds typed resources)
Consensus	Narwhal (mempool) + Bullshark (DAG-BFT)	AptosBFT (HotStuff variant), chain-BFT
Parallel execution	Object-graph based — txs touching disjoint objects parallelize trivially	BlockSTM — optimistic concurrency control + abort/retry
Latency	Sub-second for owned-object txs, ~3s for shared-object txs	~1s block time, ~1s finality
Sponsored gas	Native primitive	Native primitive
zkLogin / OAuth onboarding	Yes (zkLogin)	Yes (Aptos Keyless)
TPS (peak)	100k+ benchmark	100k+ benchmark
Major DeFi	Cetus, NAVI, Scallop, Bluefin	Thala, Aries, Liquidswap, Econia

Reading: DAG-BFT vs chain-BFT architecture gives the systems-level deeper dive.

Parallel execution — why Move L1s matter

Both Sui and Aptos pursue parallel transaction execution to escape EVM’s sequential bottleneck:

Sui’s object model makes parallelism declarative — the transaction declares which objects it touches, scheduler runs disjoint-object txs in parallel
Aptos’s BlockSTM is optimistic — execute all txs in parallel, detect conflicts, re-execute conflicting ones (similar to STM in databases)

Solana also targets parallel execution (Firedancer validator) but uses upfront-declared account accesses (Sealevel) — closer to Sui’s model than Aptos’s.

For AI-agent workloads — many concurrent micro-transactions across many wallets — parallel-execution L1s have a structural advantage over sequential L2 rollups for raw throughput (compare L2 agent economics).

Financial / agent-payment use cases

Use case	Sui	Aptos
Native USDC	Yes (Circle direct issuance, CCTP V2 supported)	Yes (Circle direct issuance, CCTP V2 supported)
Agent micropayments	Object-model + sponsored gas → fits well	BlockSTM throughput + Keyless onboarding
RWA / tokenization	Bluefin / Cetus expanding institutional features	Various RWA pilots, including USDT-equivalent attempts
Gaming / SocialFi	Strong (Suiplay devices, Mysten ecosystem)	Strong (Aptos Connect, social-graph tools)
Cross-chain	Wormhole + native bridges; [[systems/cctp-v2-overview	CCTP V2]] for USDC
Stablecoin issuance	Native USDC, USDT (eventually)	Native USDC, USDT

Both chains have integrated CCTP V2 for canonical USDC mobility, sit in the Wormhole / LayerZero mesh for general messaging, and offer sponsored-gas + Web2-friendly login that maps cleanly to AI-agent UX.

Sources

sui.io and docs.sui.io for Sui protocol and Move language documentation.
aptosfoundation.org and aptos.dev for Aptos protocol.
github.com/move-language/move for the Move language reference.
Mysten Labs and Aptos Labs research papers (Narwhal / Bullshark, BlockSTM).