Sui will add post-quantum signature schemes to let users secure accounts against future quantum-computing attacks without migrating addresses or seed phrases.
The move positions Sui among the first layer-one blockchains to natively support quantum-resistant cryptography at the protocol level. Users will be able to rotate keys to lattice-based schemes — ML-DSA and SLH-DSA, both standardized by NIST in 2024 — while keeping existing wallet addresses and recovery phrases intact.
Why the object-centric model changes the migration calculus
What triggered the move goes beyond compliance with new standards. The upgrade responds to advancing quantum timelines. NIST finalized its first post-quantum standards in August 2024, and major browsers and cloud providers have begun hybrid deployments. Sui's object-centric model allows key rotation without address changes because account ownership is tied to object capabilities rather than a fixed public key hash. This architectural difference means a user can authorize a new key pair to control the same on-chain objects without the address itself ever changing — a property that account-abstraction models on other chains must simulate through delegation contracts or proxy patterns.
How the cryptography works in practice
ML-DSA and SLH-DSA represent two distinct lattice-based approaches to digital signatures. ML-DSA, derived from the CRYSTALS-Dilithium construction, optimizes for verification speed and signature compactness, making it suitable for high-throughput environments. SLH-DSA, based on the SPHINCS+ hash-based framework, trades larger signatures for security assumptions that rest only on hash-function collision resistance. By supporting both, Sui gives wallet developers the flexibility to choose based on their users' threat models and performance requirements. The rotation mechanism itself will likely expose a transaction type that binds a new verification key to an existing account object, signed by the current key, creating a cryptographic chain of custody that validators can verify without reprocessing history.
Market context and positioning
How desks are positioning around the news reflects a broader risk-off tone. SUI traded at $0.675 on Thursday with 24-hour volume of $159.3 million, according to CoinGecko. The token has declined 2.4% in the past day and 2.8% over the week, outperforming the broader market's 0.3% dip. Market cap sits at $2.75 billion, ranking 33rd globally. Circulating supply stands at 4.07 billion tokens against a 10 billion maximum. The relatively muted price reaction suggests markets treat quantum readiness as a long-duration infrastructure bet rather than a near-term catalyst — consistent with the theoretical nature of the threat.
| Price (USD) | $0.675 |
|---|---|
| 24h Change | -2.40% |
| 7d Change | -2.80% |
|---|---|
| 24h Volume | $159.3M |
| Market Cap | $2.75B |
|---|---|
| Rank | #33 |
Why early adoption avoids future coordination failures
Why the timing matters extends beyond Sui's own roadmap. Quantum risk remains theoretical for now — no known machine can break secp256k1 or ed25519 today. But migration windows in crypto are measured in years, not months. Early adoption avoids a future coordinated hard fork across wallets, exchanges, and bridges. Sui's approach also sidesteps the address-migration friction that would accompany an Ethereum-style EIP-7702 delegation or a Bitcoin taproot script-path upgrade. On those chains, quantum-safe key rotation requires either new address formats or complex delegation layers that introduce new trust assumptions and user experience friction. By building the capability into the base protocol now, Sui shifts the cost from a future emergency migration to a present-day feature rollout.
What signals to watch for deployment
What happens next and when depends on several convergent milestones. The Sui Foundation has not published a mainnet activation date. Testnet integration is expected first, followed by wallet SDK updates from Mysten Labs and third-party providers. Key watchpoints: the release of Sui Protocol v1.40+ release candidates, wallet support announcements from Suiet, Surf, and OKX Wallet, and any validator signaling via governance proposals. A coordinated upgrade would likely require supermajority validator approval. For developers, the immediate action item is auditing whether their applications assume a fixed key type for account authorization — a pattern that will break once multi-scheme verification lands.