Sui has processed its first native post-quantum transaction on devnet, activating ML-DSA-65 as an account-level signature option months ahead of its previously outlined testnet target. The transaction demonstrates that Sui can authenticate ordinary blockchain activity using a NIST-standardized post-quantum signature scheme without changing its consensus architecture. Mysten Labs co-founder Adeniyi Abiodun confirmed the milestone following the October 12 devnet upgrade.
The implementation arrived with Sui Protocol Version 139, whose official configuration enables ML-DSA-65 account signatures on devnet. NIST standardized ML-DSA in FIPS 204 in 2024 as a lattice-based digital-signature algorithm designed to remain secure against adversaries equipped with large-scale quantum computers. Sui selected the ML-DSA-65 parameter set, corresponding to NIST security category 3, rather than the lighter ML-DSA-44 option.
NEXT MONDAY, post-quantum accounts will go live on #Sui devnet
protecting users' funds means being ready for the threats coming next
and we're well ahead of schedule pic.twitter.com/fu7Ir4ijOe
— Adeniyi.sui (@EmanAbio) October 9, 2026
Devnet Moves Sui’s Post-Quantum Roadmap Into Execution
The milestone advances Sui’s previously announced post-quantum upgrade path for accounts and vaults. ML-DSA-65 is intended for native account authentication, while a separate hash-based scheme, SLH-DSA-SHA2-128s, is being developed for high-value Move smart-contract vaults. Using two mathematically different signature families reduces reliance on a single post-quantum assumption.
Existing users are not expected to move assets into entirely new wallets when the account upgrade reaches production. Sui says quantum-resistant keys can be derived from existing recovery phrases, while Address Aliases allow an account to change its authorization key without changing the address holding its assets. The migration architecture is intended to preserve account identity and balances while replacing the cryptographic authority used to sign transactions. That mechanism forms part of the broader quantum-resistant signature infrastructure already added to Sui’s development stack.
The devnet transaction should not be interpreted as protection against an existing quantum attack. No practical quantum computer is currently known to be recovering Sui account keys in production. The upgrade is a cryptographic migration strategy for a potential future threat, not a response to evidence that Sui’s existing signatures have already been broken.
Mainnet Support Still Depends on Testing and Audits
Sui’s original August roadmap targeted native ML-DSA-65 accounts for testnet by the end of 2026 and mainnet authentication in Q1 2027. Reaching devnet in October puts the implementation ahead of that intermediate schedule, but mainnet activation remains conditional on independent security reviews, wallet and SDK integration, and feedback from wider testing.
The post-quantum transition also carries operational trade-offs. ML-DSA-65 signatures are substantially larger than today’s Ed25519 signatures, although Mysten Labs says verification performance is close enough that the network does not expect higher per-signature verification costs. Transaction size and wallet compatibility therefore become important deployment considerations even when signature verification itself remains efficient.
Other blockchain ecosystems are exploring similar migrations. Algorand has already moved native Falcon-based accounts into production usage, with Pera Wallet recording more than one million post-quantum transactions. Sui’s development differs in its use of ML-DSA-65 for normal accounts and a separate hash-based path for high-value vaults, illustrating that networks are not converging on a single post-quantum architecture.
For Sui, the October devnet transaction establishes technical feasibility at the native account layer but not production readiness. The next meaningful milestone is deployment on testnet, followed by completion of audits and eventual mainnet activation targeted for Q1 2027. Until then, existing mainnet accounts continue using the network’s current authentication schemes rather than ML-DSA-65.