CoinSearcher

On-chain methodology, source charts, protocol analysis and valuation research

Ethereum’s Post-Quantum Plan Is Also an Account-Migration Problem

As reported on November 19, 2026, Ethereum’s post-quantum work had moved beyond the question of which signature algorithm might replace today’s cryptography. The harder question is how accounts, validators and applications could change their security assumptions without leaving users unable to control existing assets. A protocol priority outlined by the Ethereum Foundation in September 2026 set December 2029 as a target, not a completed upgrade, for post-quantum resistance across Ethereum L1’s execution, consensus and data layers.

Where the risks differ

Ethereum uses cryptographic systems for different jobs. Ordinary externally owned accounts (EOAs) use ECDSA signatures; proof-of-stake validators use BLS signatures; KZG polynomial commitments support blob data availability; and some rollup proofs rely on elliptic-curve assumptions. A sufficiently capable, fault-tolerant quantum computer running Shor’s algorithm could theoretically undermine relevant public-key assumptions. No quantum computer with that cryptographic capability had emerged as of the original report.

Ethereum’s Post-Quantum Plan Is Also an Account-Migration Problem (1)

Exposure also differs between accounts. An ordinary EOA address is derived by hashing a public key with Keccak-256. If a wallet has neither sent a transaction nor publicly disclosed a signature, its full public key is not exposed through those routes. Once it sends a transaction, the public signature allows the key to be recovered. Hash functions face a different quantum-computing risk: Grover’s algorithm offers a square-root speedup, rather than the kind of break Shor’s algorithm poses to the elliptic-curve assumptions discussed here.

Three layers of proposed work

At the execution layer, native account abstraction is intended to reduce an account’s permanent dependence on one ECDSA key. EIP-8141 proposes separating transaction validation, execution and gas payment, creating room for programmable authorization and key rotation. Post-quantum signature-verification precompiles are also under study. Because replacement signatures can be much larger than existing ECDSA or BLS signatures, EIP-8288 proposes recursive STARK aggregation to reduce their on-chain data and verification burden. These are proposed mechanisms, not an assertion that existing EOAs can already switch algorithms while keeping their addresses.

Ethereum’s Post-Quantum Plan Is Also an Account-Migration Problem (2)

At the consensus layer, replacing BLS signatures would affect how validator votes are handled: a straightforward substitution with larger signatures could increase network propagation, storage and verification costs. The Lean Ethereum directions described in the report include leanXMSS, a hash-based signature approach for validators, and leanVM, intended to aggregate post-quantum signatures into compact proofs.

Ethereum’s Post-Quantum Plan Is Also an Account-Migration Problem (3)

At the data and application layers, KZG commitments and elliptic-curve-pairing-based SNARKs also warrant review. Hash-based STARKs do not rely on the same elliptic-curve discrete-logarithm assumption. A migration therefore extends beyond wallet signatures and, eventually, beyond L1 to rollups and applications.

The unresolved ownership question

A conventional EOA may need a new address if its owner moves directly to a different key system. That complicates more than transferring ETH or tokens: NFTs, DeFi positions, L2 assets and application permissions may be tied to the old address. Programmable account validation could, in principle, let an account retain its identity while changing the keys or rules that authorize it. Whether a particular account can do so depends on the mechanisms ultimately implemented.

Ethereum’s Post-Quantum Plan Is Also an Account-Migration Problem (4)

Timing matters. While an old key remains secure, its valid signature could authorize a transition to a new verification rule. If attackers could already derive or forge that key, the old signature alone would no longer establish which party is the rightful owner. Lost or inactive wallets pose a separate unresolved problem, including whether assets should remain accessible under old rules or face measures such as a freeze. Migration tools could themselves attract phishing attempts disguised as security upgrades.

The report’s conclusion was not that users needed to move assets immediately. It was that a credible post-quantum plan must address authorization, costs and safe migration together—not merely select a new signature algorithm.

Further reading