
From cryptographic agility to post-quantum security
Which blockchains are post-quantum secure?
No blockchain in this comparison is yet post-quantum across every component. Starknet is targeting full post-quantum security in 2027, Algorand also targets 2027, and Ethereum aims for December 2028, a date Ethereum Foundation researcher Justin Drake gave in his Devcon 8 talk in Mumbai on 3 November 2026, not an official Foundation roadmap change. Today, Starknet’s proving layer is hash-based, QRL signs only with hash-based signatures, and Algorand and NEAR offer opt-in post-quantum accounts. While Starknet settles on Ethereum, its bridge, messaging and data availability depend on Ethereum’s own migration; Starknet is researching whether to move to its own post-quantum L1, which would bring them under its control.
How do networks support cryptographic agility?
Our 8 questions, informed by NIST’s cryptographic agility guidance, compare how 10 networks can change cryptography and keep operating. Each evidenced capability earns one point.
Counts show evidenced capabilities within the assessed scope.
- Capability evidenced
- Rule not met or execution blocked
- Not established by reviewed evidence
Both ✕ and ? receive no point. Press a tick, a cross or a score to read its basis and evidence.
| Network | Account changeCan an existing standard account switch to a new signing scheme without a network upgrade?The account must accept independently implemented signature-checking code while keeping its identity and assets. Rotating keys or choosing an algorithm already enabled by the network alone does not count.NIST | Flexible formatsCan cryptographic interfaces accommodate different key and signature sizes without redesign?The check covers standard account formats for one working replacement, with documented key and signature sizes and resource limits.NIST | Modular updatesCan a cryptographic component be replaced without redesigning unrelated parts of the network?The component must be part of the deployed protocol, outside account signing, with its external dependencies identified.NIST | Gradual rolloutCan old and new cryptography run side by side while users migrate?Old and new account-signing methods must work side by side, with a route standard-account users can adopt today.NIST | Tested transitionHas the current cryptographic transition mechanism been tested for security and continued operation?Evidence must cover the deployed transition itself, including continued operation and security behaviour.NIST | Downgrade lockDoes the transition mechanism prevent an attacker from forcing a weaker algorithm?The check covers every authorization route on the migrated account or output. Other accounts may still use the old algorithm.NIST | Sunset mechanismCan new use of an old algorithm be disabled after migration?An enforceable rule must stop new use of the old algorithm across every authorization route on the migrated account or output.NIST | Existing dataIs there a migration mechanism for existing data that depends on the old cryptography?The check covers one named set of existing account or protocol data, preserving its integrity and authorization through migration. It does not require migrating the chain’s full history.NIST | Capabilities evidencedWithin assessed scope |
|---|---|---|---|---|---|---|---|---|---|
Cryptographic agility to quantum migration
Post-quantum migration uses cryptographic agility to move existing systems to quantum-resistant cryptography. These four stages show the broader work involved.
Identify dependencies
Find the cryptography used by accounts, protocol components and external systems.
Introduce and test
Introduce replacement algorithms, then test security, compatibility and continued operation.
Move users and data
Give users a supported upgrade path and migrate data that relies on the old cryptography.
Retire old paths
Disable vulnerable authorization paths on the migrated surface and prevent a forced return to weaker cryptography.
What shapes a network’s post-quantum migration?
The migration map considers what still needs replacing and who must coordinate that change. It groups networks by two dimensions:
- Exposure combines the evidenced status of post-quantum user signing with credit for qualifying non-signing protections already shipped.
- Friction measures how much migration asks of holders on the path securing their funds, including individual action, coordinated changes and mandatory cutoffs.
Post-quantum migration map
Higher exposure · lower friction
Exposed components, with a more adaptable replacement path within the assessed scope.
Lower exposure · lower friction
Fewer exposed surfaces within the assessed scope, with mechanisms for change.
Higher exposure · higher friction
Exposed components and a transition involving broader coordination.
Lower exposure · higher friction
Lower exposure in scope, with more coordination needed for further change.
Network evidence
View networks by group
Current map groupings, within each network’s assessed scope.
- Higher exposure, lower friction:
- None
- Lower exposure, lower friction:
- Starknet, NEAR Protocol, QRL
- Higher exposure, higher friction:
- Bitcoin, Optimism, Solana, Ethereum, Zcash
- Lower exposure, higher friction:
- Algorand
Explore the component evidence
See the changes recorded for Starknet and the architecture that supports them.
Frequently asked questions
Which blockchains support post-quantum signatures today?
Examples among the networks assessed here include:
- QRL uses XMSS signatures.
- NEAR supports optional ML-DSA-65 account keys.
- Algorand supports native Falcon-1024 accounts.
- Starknet is targeting full post-quantum security in 2027, and a post-quantum account has been demonstrated on mainnet. Standard wallets do not yet support it.
These are different levels of availability. Account-signature support does not establish that every account has migrated or that the entire network is post-quantum.
Which blockchains use post-quantum cryptography on mainnet today, and for which components?
Five of the 10 networks compared here run post-quantum cryptography on mainnet today, each in different components. As of 16 November 2026:
- QRL signs every transaction with XMSS, a hash-based signature scheme, and has done so since its 2018 launch.
- NEAR has accepted ML-DSA-65 account keys as a live opt-in since protocol upgrade 2.13 on 20 July 2026. Validator and block-production signatures remain classical.
- Algorand has accepted native Falcon-1024 accounts as a live opt-in since v5.0.0 activated around 20 August 2026. Ed25519 remains the default.
- Starknet is targeting full post-quantum security in 2027. Today, StarkWare’s hash-based STARK proofs verify Starknet’s state transitions, and Starknet v0.14.3 replaced Pedersen with a BLAKE2s-256-based construction for OS program and configuration hashes. An OpenZeppelin Falcon-512 account has been demonstrated on mainnet, but standard Starknet accounts still sign with elliptic curves.
- Solana users can adopt the Winternitz Vault, an application-layer vault that uses hash-based one-time signatures. Native Solana accounts still sign with Ed25519.
Zcash’s Ironwood notes, live since 28 July 2026, are quantum-recoverable by default, but recoverability is not post-quantum security. Running post-quantum cryptography in one component does not make a network post-quantum overall.
Which blockchains have published a plan to migrate to post-quantum cryptography?
Nine of the 10 networks compared here have published a migration plan or a formal proposal; Robinhood Chain has not. In order of stated target, as of 16 November 2026:
- Starknet is targeting full post-quantum security in 2027, under a roadmap StarkWare published on 30 June 2026. Starknet is also researching whether to move to its own post-quantum L1, after 93.52% of voting power backed the research in a non-binding October 2026 poll.
- Algorand targets 2027 for replacing its classical consensus and VRF cryptography. Its Falcon-1024 accounts are already live as an opt-in.
- Ethereum has a published post-quantum roadmap. Researcher Justin Drake gave December 2028 as Ethereum’s aim at Devcon 8 on 3 November 2026; that date is not an official Foundation roadmap change.
- Optimism: OP Labs committed in January 2026 to deprecate ECDSA-based accounts by January 2036.
- QRL plans to move holders from XMSS to ML-DSA-87 on Zond. Zond mainnet depends on audits that were about half complete in early September 2026.
- NEAR published a post-quantum roadmap in August 2026. Its ML-DSA-65 accounts are already live as an opt-in.
- Bitcoin has two draft proposals, BIP-360 and BIP-361, with no adopted timeline. BIP-361 depends on a post-quantum signature BIP that does not yet exist.
- Solana: the Solana Foundation says it would migrate if quantum computing becomes a credible threat, and Firedancer team research proposes a mechanism. Neither sets a date.
- Zcash has specified, in ZIP 2005, a future post-quantum recovery path for Ironwood notes. Its signing remains classical.
Some of these are adopted roadmaps and others are proposals; each network card above shows which.
Which blockchains target full post-quantum security by 2027?
Starknet and Algorand both state 2027 targets in their own published plans. Starknet is targeting full post-quantum security in 2027 and is researching whether to move to its own post-quantum L1, so that its remaining upgrades would not depend on Ethereum’s timeline. Full post-quantum security means every component Starknet relies on has moved off quantum-vulnerable cryptography, which, while Starknet settles on Ethereum, includes its bridge, messaging and data availability. Algorand’s 2027 target covers replacing its classical consensus and VRF cryptography; its post-quantum account signatures are already live as an opt-in. Ethereum aims for December 2028, a date Ethereum Foundation researcher Justin Drake gave in his Devcon 8 talk in Mumbai on 3 November 2026, not an official Foundation roadmap change. Ethereum plans to replace its validator signatures with hash-based signatures, which, like STARK proofs, rely on hash functions. See the Starknet roadmap →.
What do exposure and friction mean on the migration map?
Exposure combines post-quantum user-signing status with structural credit for qualifying non-signing protections. Friction measures what migration asks of holders on the path securing their funds. The migration map combines them:
- Lower exposure · lower friction.
- Higher exposure · lower friction.
- Lower exposure · higher friction.
- Higher exposure · higher friction.
Why does Starknet have more quantum exposure than NEAR and QRL on the migration map?
Because NEAR and QRL users can already sign transactions with post-quantum schemes on mainnet, and standard Starknet users cannot yet. QRL uses XMSS, a hash-based post-quantum signature scheme, as its default and only signing scheme. NEAR accepts ML-DSA-65, the post-quantum scheme NIST standardized in FIPS 204, as a live opt-in on mainnet, and its classical signature schemes remain available and have not been deprecated.
An OpenZeppelin account using Falcon-512 has been demonstrated on Starknet mainnet, but a standard Starknet user cannot adopt it yet, and standard Starknet accounts still sign with elliptic curves. Starknet gets structural credit that NEAR and QRL do not. StarkWare's STARK proofs verify Starknet's state transitions, and they rely on hash functions instead of elliptic curves.
Do Starknet, NEAR and QRL differ on migration friction?
No. All three networks sit in friction tier 2, because a holder on each one can move to post-quantum signing without waiting for a network-wide migration. A Starknet account owner can deploy or upgrade to a post-quantum account. A NEAR account owner can rotate to a new key in one transaction. A QRL holder claims funds individually to the planned ML-DSA-87 destination on Zond. The three networks sit at different points on the map because of their exposure scores
Does a checkmark in the agility table mean the network has already used that capability?
Not necessarily. It means the evidence meets that question’s pass rule. Some checks concern available mechanisms; others require a demonstrated transition. Open the cell to see exactly what was established.
Why can Bitcoin score well in the agility table and still face a difficult migration according to the migration map?
Because mechanisms for changing cryptography do not remove the need to migrate exposed coins. Holders must act, and coins whose keys are lost cannot be moved by their holders. Outputs with visible public keys, including early pay-to-public-key outputs, reused addresses and Taproot outputs, illustrate why a working upgrade mechanism alone does not complete migration. See the draft migration proposal.
Why does QRL show lower exposure and friction on the migration map without a perfect score in the agility table?
Because QRL’s XMSS hash-based signatures avoid an elliptic-curve signing legacy, while the table tests a wider set of change mechanisms. Its planned move to another post-quantum scheme also shows why cryptographic agility continues to matter.
Why does Zcash still show higher exposure on the migration map?
Because its current signatures, proofs and note encryption still have quantum-vulnerable dependencies. Ironwood adds quantum-recoverable notes and a supported route to migrate existing funds. It prepares notes for a future recovery protocol. The agility table credits evidenced migration mechanisms, while the migration map reflects the replacements still required.
Why does NEAR support post-quantum signing but miss Account change in the agility table?
Because adopting a protocol-supported signing scheme is different from installing independently implemented verification code. NEAR’s native ML-DSA-65 keys let existing accounts adopt a protocol-supported signing scheme. The migration map recognises lower friction for the live account path; validator and block-production signatures remain classical.
Which Starknet protocol changes have shipped, and what remains?
The migration register records v0.14.3’s mainnet replacement of Pedersen with a BLAKE2s-256 construction for OS program and configuration hashes. Trie and contract-address changes remain roadmap direction. Tooling for existing contracts with Pedersen-based storage maps remains research, without a published specification or released toolkit.
How does Ethereum affect Starknet’s migration?
It creates migration work that Starknet cannot complete on its own. Starknet normally publishes state diffs as Ethereum blobs, which depend on Ethereum’s KZG scheme. Starknet does not control that scheme’s migration; calldata is an available fallback. See the Ethereum-facing dependency record.
How can I check Starknet’s assessment?
Open a table cell or map circle to inspect its basis and public sources. StarkWare produced the agility table and migration map and is a core developer of Starknet, one of the networks assessed. The agility table’s pass rules were fixed before scoring. Use the migration register to check Starknet’s deployment boundaries.
How can I request a change to the comparison?
Email james.w@starkware.co with the network, the agility table criterion or migration map placement, your suggested change, and links to supporting evidence.
Can Ethereum accounts switch to post-quantum signatures?
It depends on the account. Ordinary Ethereum accounts still use secp256k1 signatures. ERC-4337 smart-contract accounts can implement custom verification, including a suitably implemented post-quantum verifier. That requires a compatible account, wallet and migration path. EIP-7702 delegation alone does not remove the original account’s signing authority.