Commitments
Post-quantum commitments
Every delivery date a rated chain has published for its post-quantum work, and whether the date has passed. As of 13 November 2026.
This record is published beside the Hardy Score and is not an input to it. No chain is ranked here and no ratio is computed. A weight on deadlines missed would mark down the chain that publishes an honest, dated roadmap against one that publishes nothing, and the methodology sets out why that is the wrong incentive.
- A target is listed only where the chain's foundation, its core development team or a formally adopted improvement proposal published the date. A third party's estimate is not a target.
- A target stated as a quarter, half or year is due on the last day of that period.
- A target that has passed is shown as under review for 14 days, so a delivery the dataset has not yet recorded can be checked, and as past target after that.
- When a chain moves a date, the earlier target stays on the record.
Past target 1
| Chain | Commitment | Target | Status |
|---|---|---|---|
| XRP Ledger | An assessment of the full impact of post-quantum cryptography on the XRPL: a network-wide quantum-risk assessment, experimentation with NIST-recommended signature schemes measured for signature size, verification cost and throughput, and, with Project Eleven, a proof-of-concept hybrid signing implementation with validator testing, Devnet benchmarking and a custody wallet prototype. Early ML-DSA proof-of-concept work on AlphaNet was already underway when the plan was published. As of 21 October 2026 we found no published assessment or benchmark results, which is what this target is past due for. | First half of 2026 due by 30 June 2026 | Past target |
Open 15
| Chain | Commitment | Target | Status |
|---|---|---|---|
| Akash Network | AEP-79, by Greg Osuri, sets out Akash's move from its sovereign chain to another network. The AEP is marked Final and appears on Akash's 2026 roadmap with an estimated completion of 31 December 2026. The migration itself was not put to a governance vote until proposal 346, which passed on 2 November 2026. It does not address post-quantum signatures. | estimated completion 31 December 2026 due by 31 December 2026 | Open |
| Algorand | Native Falcon-512 support, the smaller Falcon parameter set with signatures roughly half the size, which Algorand plans to add by the end of 2026. | Planned for year's end due by 31 December 2026 | Open |
| Algorand | Native multisig across signature schemes, so a single m-of-n account can mix classical, Falcon and hybrid keys. Until it ships, Algorand points treasuries to post-quantum multisig built on LogicSigs. | By the end of 2026 due by 31 December 2026 | Open |
| Algorand | Staking from post-quantum accounts. The Algorand Foundation announced that stakers will be able to stake from them, alongside post-quantum multisig, later in 2026. | Later this year due by 31 December 2026 | Open |
| Stellar | Add post-quantum signature verification to Soroban as native host functions supporting ML-DSA-44 and ML-DSA-65, with contract accounts able to implement quantum-safe authentication through account abstraction. | 2026 (Stage 1) due by 31 December 2026 | Open |
| Sui | Quantum-safe smart contract vaults using SLH-DSA targeted for mainnet. | 2026 due by 31 December 2026 | Open |
| Sui | Native ML-DSA-65 accounts on testnet. | End of 2026 due by 31 December 2026 | Open |
| XRP Ledger | Hybrid deployment of post-quantum and elliptic-curve signatures on Devnet, plus exploration of post-quantum primitives for zero-knowledge proofs and homomorphic encryption. | Second half of 2026 due by 31 December 2026 | Open |
| Gnosis Chain | Genesis of the Gnosis rollup under GIP-153: the validator set is sunset and the first block is produced on the new design, conditional, as GIP-153 states, on the broader Ethereum Economic Zone dependencies landing. It does not address post-quantum signatures. | December 2026/ Jan 2027 due by 31 January 2027 | Open |
| Ozone Chain | Ozone's roadmap lists "Setup Quantum Tunnels between the Nodes", the post-quantum encrypted links its whitepaper describes. These would protect traffic between nodes, not the signatures on funds. The roadmap first gave Q4 2024, a date it still showed in January 2026; by 11 March 2026 the item had moved to Q3 2026, by 21 May 2026 to Q4 2026, and by 4 November 2026 to Q1 2027. Moved from Q4 2024 (replaced 11 March 2026), Q3 2026 (replaced 21 May 2026), Q4 2026 (replaced 4 November 2026) . | Q1 2027 due by 31 March 2027 | Open |
| Sui | Native post-quantum account authentication on mainnet. | Q1 2027 due by 31 March 2027 | Open |
| Algorand | Broad quantum resilience across the protocol, including research into a post-quantum VRF and post-quantum signatures for consensus messages. | End of 2027 due by 31 December 2027 | Open |
| Hedera | A new post-quantum key type for users, with existing Ed25519 and ECDSA keys continuing to work alongside it. | 2027, or on FIPS 206 publication if sooner due by 31 December 2027 | Open |
| XRP Ledger | A new amendment proposing native post-quantum cryptography for the XRPL, with network-wide deployment. | No later than 2028 due by 31 December 2028 | Open |
| Ethereum | Structured fork milestones target completion of core post-quantum infrastructure. | Approximately 2029 due by 31 December 2029 | Open |
Delivered 1
| Chain | Commitment | Target | Status |
|---|---|---|---|
| Algorand | Native Falcon-1024 accounts activate on mainnet with the go-algorand 5.0.0 consensus upgrade, at round 64,318,659. Existing accounts can be rekeyed to a Falcon-1024 key and keep their address, and Pera Wallet supports creating and rekeying to quantum accounts. Delivered inside the Q3 2026 window the roadmap gave. | Native post-quantum accounts in the Q3 2026 protocol release due by 30 September 2026 | Delivered on time 22 August 2026 |
Coins that never migrate
Every chain eventually has to say what happens to coins whose holders never move them to post-quantum keys: sunset the old signatures, freeze the coins, offer a way to recover them, or leave them alone. 9 of 80 rated chains have a formal position. Checked against each chain's own published material; "no stated policy" means nothing was found there, not that nobody is discussing it.
| Chain | Stance | What it says |
|---|---|---|
| Zcash | Adopted Recover with a post-quantum proof | ZIP 2005, deployed with the NU6.3 upgrade, makes new notes recoverable through a future post-quantum recovery protocol. The ZIP states that funds left in older shielded pools would become inaccessible if those pools are disabled. The recovery protocol itself is not yet specified. source |
| Bitcoin | Proposed Sunset legacy signatures | Draft BIP-361 would first allow legacy outputs to send only to post-quantum outputs, then at a later flag day stop accepting ECDSA and Schnorr spends, leaving coins that have not moved unspendable unless a rescue protocol is defined. It has no activation path. source |
| Cardano | Proposed Recover with a post-quantum proof | Draft CIP-0197, an open pull request, proposes zero-knowledge proofs of a wallet seed alongside Ed25519 signatures, which its author and reviewers frame as a recovery path for addresses that never migrate. source |
| Polkadot | Proposed Recover with a post-quantum proof | The Web3 Foundation research team's post-quantum roadmap proposes migrating accounts with a one-time proof of knowledge of the seed behind the existing key, so cold wallets need no post-quantum key set in advance. It is a roadmap post, not an adopted RFC. source |
| Sei | Proposed Sunset legacy signatures | Draft SIP-5 proposes a governance-set cutoff height after which accounts with no post-quantum key can still receive funds and be called, but can no longer originate transactions. It provides no recovery path and leaves any recovery to a separate SIP. source |
| Stellar | Proposed Sunset legacy signatures | The Stellar Development Foundation's Quantum Preparedness Plan sets a later stage after which Ed25519 signatures are no longer accepted, and leaves open whether dormant accounts are then recoverable by a proof of their seed or locked permanently. source |
| Tezos | Proposed Recover with a post-quantum proof | The core developers' plan says that if users have not moved to a post-quantum key by a fencepost date, the protocol may still require a post-quantum zero-knowledge proof of knowledge of the seed words. It is stated as a possibility, not a design. source |
| Tron | Proposed Sunset legacy signatures | Draft TIP-899 makes post-quantum keys voluntary and lists, as an untimed future phase, a network rule accepting only post-quantum signatures. What would happen to accounts that never move is not specified. source |
| XRP Ledger | Proposed Recover with a post-quantum proof | Phase 1 of Ripple's post-quantum roadmap explores zero-knowledge proofs of ownership of existing seed-based keys, so funds could still move to post-quantum accounts after classical signatures stop being accepted. source |
No stated policy (65): 0G, AIOZ Network, Akash Network, Algorand, Aptos, Arweave, Avalanche, Beldex, Bitcoin Cash, Bitcoin SV, Bittensor, BNB Chain, Celestia, Chiliz Chain, Conflux, Cosmos Hub, Cronos, Dash, Decred, Dogecoin, dYdX Chain, eCash, Ethereum, Ethereum Classic, Filecoin, Flare, GateChain, Gnosis Chain, Hedera, Hyperliquid, Injective, Internet Computer, IOTA, Kaia, Kaspa, KCC (KuCoin Community Chain), Kite, Litecoin, MemeCore, Midnight, Mina Protocol, Monad, Monero, MultiversX, NEAR Protocol, Neo, Nervos CKB, Nexus, Ozone Chain, Polygon PoS, Provenance Blockchain, QoreChain, Qtum, Solana, Sonic, Sui, Terra Classic, Theta Network, THORChain, TON, Vaulta, VeChain, WEMIX, Whitechain, XDC Network.
Not applicable (6): Abelian, Dilithion, Mochimo, Quantum Resistant Ledger, Quantus Network, Tidecoin, which have used post-quantum signatures from the start.