Block Beacon Chain

A beacon is a schedule, not a mood.

Ethereum’s Post-Quantum Plan: What Would Change for Validators and Wallets?

As reported on November 19, 2026, Ethereum’s post-quantum work was a long-term engineering effort, not a response to a quantum computer already capable of breaking the network’s cryptography. The report said the Ethereum Foundation had formed a Post-Quantum Security team and, in protocol priorities published that September, set a goal of making Ethereum L1 resistant to quantum attacks across its execution, consensus and data layers by December 2029. That date was a target, not an activated upgrade.

Why the risk differs across accounts and validators

A sufficiently capable, fault-tolerant quantum computer running Shor’s algorithm could, in theory, undermine the elliptic-curve assumptions behind two different kinds of Ethereum signatures. Ordinary externally owned accounts use ECDSA to authorize transactions. Proof-of-stake validators use BLS signatures, whose aggregation helps the consensus layer handle votes from large numbers of validators. A replacement therefore has to account for both wallet authorization and the cost of circulating and verifying validator signatures.

Ethereum’s Post-Quantum Plan: What Would Change for Validators and Wallets? (1)

Exposure also differs between user accounts. An ordinary Ethereum address is derived from a hash of its public key. If an account has never sent an on-chain transaction or disclosed a signature elsewhere, its full public key may not be public. Once it signs a transaction, the public key can be recovered from the public signature, creating a more direct exposure if elliptic-curve cryptography becomes breakable. This is a future threat model, not a claim that such an attack was possible when the report was published. The report said no quantum computer with that cryptographic capability had emerged.

Ethereum’s Post-Quantum Plan: What Would Change for Validators and Wallets? (2)

The proposed changes span three layers

On the execution layer, the difficulty is not simply generating a new key. A conventional account’s address and authorization are tied to its existing signing scheme, while its assets and application relationships may extend across tokens, NFTs, DeFi positions and L2 networks. EIP-8141, discussed in the report as a native account-abstraction proposal, aims to separate transaction validation, execution and gas payment so that programmable authorization could support changes to an account’s keys or verification rules. It does not mean existing accounts can already rotate to post-quantum signatures while retaining their addresses. The report also described research into post-quantum signature-verification precompiles and EIP-8288’s proposed use of recursive STARK aggregation to reduce the burden of larger signatures.

Ethereum’s Post-Quantum Plan: What Would Change for Validators and Wallets? (3)

On the consensus layer, replacing BLS signatures without another means of aggregation could increase the network, storage and verification costs of validator participation. The Lean Ethereum directions described in the report include leanXMSS, a hash-based signature approach proposed for validators, and leanVM, intended to help aggregate post-quantum signatures into compact proofs. These were research directions, not changes already made to validator duties.

Ethereum’s Post-Quantum Plan: What Would Change for Validators and Wallets? (4)

On the data layer, KZG commitments used with blobs and rollup data availability rely on elliptic-curve pairing assumptions. The report also noted that some application-layer SNARKs have similar dependencies, whereas hash-based STARKs avoid the elliptic-curve discrete-logarithm assumption. Post-quantum planning therefore reaches beyond account and validator signatures to data commitments, L2s and applications.

Ethereum’s Post-Quantum Plan: What Would Change for Validators and Wallets? (5)

Migration has to happen while old authorization remains trustworthy

The report’s central wallet problem was how a user could authorize a new key without losing control of an existing account. In a possible future upgrade flow, a wallet would create a post-quantum key and use the current account’s valid signature to approve a change in verification rules. That only provides a clear authorization path while the old key remains secure. If an attacker can already forge signatures under the old scheme, an old-key signature alone cannot establish which claimant is the owner.

Ethereum’s Post-Quantum Plan: What Would Change for Validators and Wallets? (6)

Dormant accounts and lost keys pose a separate problem: their owners may be unable or unaware they need to migrate. Whether such assets should remain at their addresses or face measures such as a freeze was described as a matter of debate, not an adopted rule. The report also warned that purported “quantum-safe upgrade” or migration pages could be used to solicit seed phrases or malicious approvals.

For readers and wallet developers, the distinction is between preparing a verifiable migration path and rushing to move assets. As of the original November 2026 reporting, the described quantum threat was not an immediate reason for users to transfer funds; the proposed protocol and wallet changes still required substantial work.