Algorand Adds Falcon Accounts, Sets 2027 Quantum Goal

By Nathan Brooks

Algorand added Falcon-1024 account support to its mainnet in August, advancing the network’s post-quantum security work while leaving its verifiable random function and consensus signing on existing cryptography.

Algorand CEO William Herkelrath said institutions are “taking more interest in post-quantum security.” His statement connects that interest to Algorand’s work to extend quantum-resistant protections beyond accounts, with broader network resilience targeted by the end of 2027.

The National Institute of Standards and Technology (NIST) selected Falcon as a signature scheme, and Algorand’s implementation uses Falcon-1024 for accounts. The mainnet addition gives the account layer a post-quantum option, but it does not make every Algorand operation post-quantum resistant. Algorand’s roadmap distinguishes that narrower deployment from its broader goal.

What does this change for institutions?

For institutions assessing tokenized-market infrastructure, the practical change is a new control to evaluate at the account layer. They can now include Falcon-1024 support when reviewing how Algorand secures accounts instead of treating post-quantum readiness as only a future roadmap item.

The upgrade should not be read as network-wide completion. Three technical areas remain relevant:

• Accounts: Algorand added Falcon-1024 support to mainnet in August.
• Verifiable random function: It still uses elliptic-curve cryptography.
• Consensus signing: The network still uses Ed25519.

The stated migration therefore reaches one of three named areas. The account layer has a NIST-selected post-quantum option, while two systems retain their existing algorithms. This distinction matters because adding a post-quantum signature at the account layer does not remove legacy cryptography from every operation supporting consensus or randomness.

For an institutional risk team, the useful distinction is between component-level cryptographic coverage and network-wide assurance. Falcon-1024 addresses one part of the former; the two unchanged systems determine how far the latter extends. That separation matters in architecture plans, vendor reviews and internal controls because no single label can replace a component-level inventory.

Algorand’s end-2027 goal covers a broader migration than the August release. It signals a staged effort in which institutions may encounter quantum-resistant account support before the network reaches its wider resilience objective. The deadline provides a boundary for the roadmap, not evidence that every component will be ready on the same schedule.

Herkelrath previously called for financial firms to “plan for post-quantum protections in tokenized markets.” In that context, the new mainnet capability provides a concrete deployment for part of that planning, while the 2027 target defines the remaining institutional horizon.

The statement does not identify financial institutions that have adopted Falcon-1024. It concerns institutional interest, not disclosed adoption. Even so, Algorand is presenting post-quantum security as an infrastructure requirement rather than a distant research topic, and it expects institutional scrutiny to extend beyond accounts.

What the August change does not do is establish post-quantum protection across Algorand’s full network. For practitioners, the relevant review is therefore component by component: account signatures now have a NIST-selected option, while the verifiable random function and consensus layer retain their existing algorithms.

That distinction should remain central until Algorand replaces those systems or publishes more detailed implementation milestones. The end-2027 deadline gives the project a defined horizon, but the mainnet account release is an intermediate milestone, not completion of the network-wide transition.