Hardy Index Quantum readiness, rated and tracked

What changed · What changed

We corrected the Algorand profile: Falcon-1024 accounts have been live since 22 August

The profile sat eight weeks behind the chain, and the migration scoring was the part that was wrong.

The short answer

On 19 October 2026 we corrected the Algorand profile. Native Falcon-1024 accounts have been live on mainnet since 22 August 2026, so the migration dimension moved into its top band: holders can rekey an existing account today. The tier and the rank did not change, and Ed25519 is still the default.

What we got wrong, and what we fixed

The correction was recorded on 19 October 2026. Until then, the Algorand profile still listed native Falcon-1024 accounts as in progress for the third quarter of 2026, and the migration dimension was held down on the stated ground that holders could not yet move. That ground had not been true since 22 August.

The go-algorand 5.0.0 consensus upgrade makes Falcon-1024 a native account type. Falcon is a lattice based signature scheme chosen by NIST, and the point of a native account type is that the protocol itself checks the signature rather than a contract doing it on the side. The upgrade activated on mainnet at round 64,318,659, the first block produced under consensus version V42. We read the round and the version from block headers on a public mainnet node before changing anything.

An existing account can be rekeyed to a Falcon-1024 key. It keeps its address, its assets and its history, and after the rekey the protocol ignores signatures from the old Ed25519 key. Pera Wallet supports both creating a quantum account and rekeying an old one to it. That meets the top migration band: a holder can migrate today, with the wallet they already use.

A second correction sits in the same entry. In August the signature dimension was raised when the 5.0.0 release was published, nine days before the upgrade activated on mainnet. Under our own rule, code only counts once it is live. The level it reached was correct from 22 August and stands, but the move was early, and the record now says so.

Where Algorand sits now

Where this stands today

As rated by the Hardy Index, current as of 17 November 2026. Ratings change when the evidence does, and every change is recorded in the changelog.

The band change lifted the overall score but not the tier, and the rank is unchanged. We covered the original shipping event in Algorand just shipped the thing we said to watch for.

What this does not mean

Migration being possible is not migration being done, and it is not the default.

  • New accounts are still Ed25519 unless you choose otherwise. Nothing about your balance changed on 22 August.
  • The route is opt-in, account by account. There is no network wide sweep that protects everyone at once.
  • Some dApps do not yet handle quantum accounts, so a rekeyed account may hit friction in places.
  • Post-quantum multisig is not available yet. Treasuries and anyone on a multi-signer setup cannot make this move today.
  • Falcon-512 and native multisig across signature schemes are both targeted for the end of 2026.

We also narrowed the roadmap entry to what the source actually says.

Correction, 21 October 2026This post first said scheme-agnostic multisig had no published date, and that we had removed a staking claim because the source did not mention it. Both were wrong. Algorand's roadmap of 18 June dates native multisig across signature schemes to the end of 2026, and the Foundation's press release the same day says stakers will be able to stake from post-quantum accounts. The staking claim was supportable; it had been cited to the wrong page. Both are now on the profile with those sources.

If you hold ALGO

The practical change is that the option is real and you can check it yourself. Rekeying is a protocol level feature, documented, and supported in a mainstream wallet. If you hold a single-signer account and you care about long lived key exposure, the path exists now rather than later.

If you hold through a custodian, an exchange or a multisig, the path does not exist for you yet, and that is the gap worth tracking. Our guide to moving to a quantum ready chain sets out what to look for before you move anything.

Why this entry existsWe log corrections in the same feed as rating changes. A profile that is eight weeks behind the chain is a defect in the index, not a detail.

Timeline

Algorand's native Falcon-1024 accounts, from release to activation.

  1. The go-algorand 5.0.0 release is published, adding Falcon-1024 as a native account type. source
  2. The consensus upgrade activates on mainnet at round 64,318,659, the first block under consensus version V42. source

Where to go next

Sources

Every dated event above carries its own primary source. These are those sources, each checked on the date shown.

  1. go-algorand v5.0.0-stable release notes Algorand (GitHub) · primary · checked 20 October 2026
  2. Post-quantum technology overview Algorand · primary · checked 20 October 2026
  3. Create or upgrade to a quantum account on Pera Wallet Pera Wallet support · primary · checked 20 October 2026
  4. Rekeying Algorand developer docs · primary · checked 20 October 2026
  5. Algorand targets broad quantum resilience by 2027 Algorand · primary · checked 20 October 2026
  6. Technical brief: quantum resistant transactions with Falcon signatures Algorand · primary · checked 20 October 2026
  7. Algorand Foundation Announces Post-Quantum Security Roadmap Algorand Foundation · primary · checked 21 October 2026
  8. Algorand Post-Quantum Cryptography Roadmap Algorand Foundation · primary · checked 21 October 2026

This is a security-readiness assessment, not investment advice.