Ethereum’s Post-Quantum Roadmap: The Protocol Changes and the Account-Migration Problem

In a November 19, 2026 account of Ethereum’s post-quantum work, imToken described a long-term challenge: replacing vulnerable cryptographic tools without leaving users unable to control their existing assets. The account said the Ethereum Foundation had formed a Post-Quantum Security team and had set an engineering goal, announced in September 2026, of making Ethereum L1 post-quantum-resistant across its execution, consensus and data layers by December 2029. That goal is not an activated network upgrade.

What would need to change?

A sufficiently capable, fault-tolerant quantum computer running Shor’s algorithm could, in theory, undermine the elliptic-curve assumptions behind ECDSA account signatures and BLS validator signatures. An attacker able to derive a private key from a public key could forge signatures without stealing a seed phrase. imToken noted that no quantum computer capable of breaking this cryptography existed at the time of its report.

Ethereum’s Post-Quantum Roadmap: The Protocol Changes and the Account-Migration Problem (1)

Exposure differs between accounts. An ordinary externally owned account (EOA) address is derived from a hashed public key. If its public key has not been revealed through a transaction signature or an off-chain signature, the address alone does not expose that key. A signed transaction, including a transfer or contract approval, can make the public key recoverable from the signature.

Ethereum’s Post-Quantum Roadmap: The Protocol Changes and the Account-Migration Problem (2)

Other components present different migration problems. Ethereum uses BLS signatures to aggregate validator votes, while KZG commitments support blob and rollup data availability. Some pairing-based zero-knowledge proofs also rely on assumptions vulnerable to a future quantum attack. Hash-based constructions, including STARKs, do not rely on the same elliptic-curve discrete-logarithm assumption.

Ethereum’s Post-Quantum Roadmap: The Protocol Changes and the Account-Migration Problem (3)

Proposed paths, not deployed replacements

On the execution layer, EIP-8141 is presented as a native account-abstraction proposal that would separate transaction validation, execution and gas payment. Programmable validation could give accounts a path to changing keys or signature methods without tying control permanently to one ECDSA key. Research into post-quantum signature-verification precompiles addresses another part of that path. EIP-8288 proposes recursive STARK aggregation to reduce the on-chain burden of verifying larger post-quantum signatures. Neither proposal should be read as an already deployed account-migration mechanism.

Ethereum’s Post-Quantum Roadmap: The Protocol Changes and the Account-Migration Problem (4)

For consensus, the Lean Ethereum directions described by imToken include leanXMSS, a proposed hash-based alternative to validator BLS signatures, and leanVM, intended to help aggregate post-quantum signatures into compact proofs. Replacing BLS directly with larger signatures would raise propagation, storage and verification costs. KZG commitments and affected rollup proof systems would require separate consideration; changing wallet signatures alone would not complete the migration.

Ethereum’s Post-Quantum Roadmap: The Protocol Changes and the Account-Migration Problem (5)

The unresolved user transition

A new key is not necessarily a seamless replacement for an old EOA. Moving to a new address could mean handling ETH, tokens, NFTs, DeFi positions, L2 assets and application permissions tied to the original address. Programmable account validation could, in principle, let some accounts change their authorization rules while retaining their identity, but a workable path depends on the account and the eventual deployed rules.

Ethereum’s Post-Quantum Roadmap: The Protocol Changes and the Account-Migration Problem (6)

Timing matters. While an old key remains secure, its valid signature could authorize a transition to a new key. If that key can already be derived by an attacker, the old signature alone may no longer distinguish the owner from an impostor. imToken also identified unresolved questions about dormant or inaccessible accounts, including whether assets should remain at old addresses or face a future governance decision such as freezing. No such freeze is described as enacted.

The report did not call for users to move assets immediately. It warned instead that purported “quantum-safe” upgrades or migration pages could become a phishing pretext. The protocol roadmap and a safe, understandable wallet migration process are related—but distinct—pieces of the work ahead.

Further reading