// the find
MystenLabs/sui
Sui, a next-generation smart contract platform with high throughput, low latency, and an asset-oriented programming model powered by the Move programming language
Sui is a Layer 1 blockchain written in Rust that uses a variant of Meta's Move language for smart contracts. Its core architectural bet is separating owned-object transactions (no consensus needed, sub-second finality via validator quorum) from shared-object transactions (full consensus, slower). Target audience is teams building latency-sensitive apps — gaming, payments — who need predictable throughput and are willing to learn Move.
The owned-object fastpath is technically sound: transactions touching only owned objects skip consensus entirely and get finality from a simple 2f+1 quorum signature, which is why Sui can credibly claim sub-second settlement for the common case. Move's type system enforces linear resource ownership at the language level — you cannot accidentally drop or duplicate a coin type, and the compiler rejects it rather than relying on runtime guards. The consensus layer is a cleanly separated crate (consensus/core) implementing a DAG-based BFT protocol, and it ships with its own simulation test harness (simulacrum + consensus/simtests) that can inject faults deterministically. The CI infrastructure is genuinely mature for a blockchain project: sccache warming, nextest, insta snapshot tests, and separate nightly simulator runs.
Move's developer pool is tiny. Outside Sui and Aptos, the language has almost no ecosystem — no battle-tested DeFi libraries, no established audit firms with deep Move expertise. Any shared-object workload (AMMs, order books, lending) hits full BFT consensus and loses Sui's headline performance advantage; the gap between owned and shared latency is large enough that application architecture is severely constrained by it. The monorepo is enormous — 400+ crates — and the boundary between sui-core, sui-execution, and the consensus crate is not obvious from directory structure alone; onboarding a new contributor to the execution layer takes days just navigating dependencies. The bridge (bridge/evm/contracts/SuiBridge.sol) is a separate Solidity implementation with its own committee signing scheme, meaning there are now two security models to audit rather than one.