Sui Adds NIST-Approved Quantum Signatures After AI Finds Crypto Weakness

MakeCryippreferred on

Sui is adding two NIST-approved post-quantum signature schemes: ML-DSA-65 natively for regular accounts and SLH-DSA-SHA2-128s inside Move contracts for high-value vaults. Existing accounts can migrate using their current recovery phrase while keeping the same address. Sui chose costlier security parameters after an AI model found a way to weaken a separate, unrelated candidate scheme.

The rollout begins with quantum-safe vaults targeted for Mainnet this year, followed by native ML-DSA-65 accounts on Testnet by the end of 2026 and full account authentication on Mainnet in the first quarter of 2027. According to Sui’s announcement, existing users will be able to derive quantum-safe keys from their current recovery phrases while keeping the same wallet address through its address alias system. The upgrade is designed to let users adopt post-quantum protection without transferring funds or creating new accounts.

Making Sui quantum ready: Sui is adding two NIST-approved quantum-resistant signature schemes. One for everyday accounts, one for high-value Move vaults.

Existing accounts can rotate to a quantum-safe key derived from their recovery phrase. Same address, and funds stay put.

— Sui (@SuiNetwork) August 6, 2026

Two Schemes, Two Threat Models

ML-DSA-65 (FIPS 204) is a lattice-based signature scheme that becomes Sui’s native protocol signature for regular transactions. SLH-DSA-SHA2-128s (FIPS 205) is hash-based and runs inside Move contracts, where it is reserved for high-value vaults. By combining two schemes built on different mathematical foundations, Sui aims to reduce the risk that a weakness in one family would affect the other.

Why Level 3, Not Level 1

Within ML-DSA, Sui chose the costlier Level 3 parameter set over the cheaper Level 1. The stated reason: in July 2026, an AI model found a way to cut the effective key strength of HAWK, a separate post-quantum signature candidate, in half after roughly 60 hours of work, on a scheme that had already survived two years of expert human review. Sui says the finding doesn’t affect ML-DSA, and the underlying math supports that: HAWK’s lattice problem and ML-DSA’s Module-LWE structure are different enough that the same attack doesn’t carry over. Sui is citing the result anyway, as a reason to carry security margin rather than take the cheapest parameters on offer.

Same Recovery Phrase, Same Address

For accounts already in use, Sui’s migration path avoids the usual bottleneck in any cryptographic transition: getting people to actually move. An ML-DSA-65 private key on Sui is a 32-byte seed, the same size current wallet keys already are, derived from the same recovery phrase through a new derivation path. Existing accounts use address aliases, already live on Sui, to update their authorization key without transferring funds or changing addresses. The focus on secure account migration comes as Sui also works to strengthen network resilience following the recent Sui Mainnet Halt.

The Tradeoff Sui Says Doesn’t Bite

Post-quantum signatures and public keys are bigger than the Ed25519 pairs they replace, which pushes up transaction size industry-wide. Sui’s claim is that the more expensive half of that tradeoff, verification cost, doesn’t materialize: ML-DSA-65 verification on Sui is close enough to Ed25519 that per-signature network cost stays flat, with the larger size absorbed by Sui’s transaction size limit and programmable transaction blocks. This broader focus on transaction-level security also complements Sui Confidential Transfers, which is designed to add privacy to blockchain transactions while supporting compliance-focused use cases.

Where Sui Actually Sits

Sui’s dated rollout puts it ahead of Bitcoin and Ethereum. One industry assessment puts both chains in early roadmap or discussion phases, with no binding protocol commitments on quantum resistance yet. This builds on Sui’s broader security efforts, including Sui Seal MPC, while it sits behind Algorand, whose Falcon-1024 post-quantum scheme has been live on mainnet since November 2025.

BNB Chain, in its own May 2026 migration report, flagged network scaling from larger signatures, not cryptographic strength, as the industry’s likely bottleneck. Sui’s vault-level signatures, kept inside Move contracts rather than the protocol core, don’t avoid that size cost. What the contract-level placement buys instead, per Sui’s own reasoning, is the ability to stay compatible with whichever post-quantum standard the wider industry eventually settles on, without a core protocol upgrade.

Rollout Roadmap

• Now: Independent audits underway; core implementation built and benchmarked
• This year (2026): Quantum-safe vaults targeted for Mainnet
• End of 2026: Native ML-DSA-65 accounts targeted for Testnet
• Q1 2027: Native account authentication targeted for Mainnet

FAQs

1. What’s actually changing for existing Sui accounts?
Nothing by default. When available, moving to a quantum-safe key is opt-in, using the recovery phrase you already have, with no address change and no fund transfer.

2. Why does Sui need two different schemes instead of one?
ML-DSA and SLH-DSA rest on different mathematical foundations. A weakness discovered in one wouldn’t extend to the other.

3. Is Sui vulnerable to quantum attacks right now?
No practical quantum computer capable of this exists today. The exposure Sui is addressing is sometimes called “harvest now, decrypt later”: collecting an exposed public key today, to attack once quantum hardware exists later.