Algorand has shipped go-algorand v5.0.0, a consensus upgrade release that embeds post-quantum account security directly into the protocol rather than layering it on top via workarounds.The release now moves to a governance step: node runners will vote on whether to activate the consensus upgrade. If the vote passes, accounts will be able to use Falcon-1024 signatures at addresses that no Ed25519 key could ever control, drawing a clean cryptographic boundary between legacy and quantum-resistant accounts.
That added security comes with trade-offs. Falcon-1024 transactions cost three times the standard minimum fee, and the signatures cannot be batch verified, meaning each one must be checked individually. Developers and users choosing post-quantum accounts should factor both costs into their workflows.
The v5.0.0 release also brings support for larger app sizes and AVM v13 , with the smart contract size limit doubling to 16,384 bytes. Crucially, live applications can grow into that expanded limit without being redeployed, which removes a significant operational burden for teams running production contracts.
Part of a Broader Quantum-Resistance Push
The first post-quantum transaction hit Algorand’s mainnet on November 3, 2025, using Falcon signatures. Since then, over 140,000 such transactions have been processed. The v5.0.0 upgrade represents the next logical step: moving from Falcon accounts backed by LogicSignatures to native protocol-level support.
The Q3 2026 protocol release introduces network-level support for multiple concurrent signature schemes, a foundational step toward cryptographic agility, while continuing to support traditional Ed25519 accounts alongside the new Falcon-1024 scheme.
In June 2026, Algorand announced a roadmap targeting broad quantum resilience by the end of 2027, covering native post-quantum accounts, post-quantum multisig for institutions and treasuries, and research into post-quantum-resilient VRF and signatures for consensus messaging.