Ethereum Commits to Quantum Resistance by End of 2029

The Ethereum Foundation has pledged to shield Ethereum (ETH) from quantum computing threats by December 2029, treating that date as a hard deadline rather than a research objective.

The Protocol cluster released that target alongside its evaluation of 62 proposals for Hegotá, the hard fork that follows Glamsterdam.

Ethereum Sets a Hard Deadline It Cannot Push Back

The Foundation requires Ethereum's base layer to be quantum-resistant across execution, consensus, and data. Its priorities blog states the network must prepare for Q-day possibly arriving as early as 2030.

This deadline matches migration schedules independently established by Google, Cloudflare, and Microsoft. The Foundation acknowledged it is ahead of most credible forecasts.

“Planning for Q-day in 2030 is a deliberately aggressive assumption,” the blog reads.

The cluster will consider the deadline non-negotiable at least until January 2027, when external experts help reassess quantum progress. Roughly 65% of ETH already sits in addresses vulnerable to quantum attacks, according to Project Eleven.

Hegotá Will Test Whether the 2029 Commitment Is Achievable

Hegotá was framed by the Foundation as the fork that decides whether later post-quantum upgrades arrive on schedule. Full quantum resistance is five hard forks away, and hitting December 2029 would require an average of 7.2 months per fork, a pace the cluster itself calls aggressive.

Frame Transactions is the must-ship execution-layer component, opening a path to new signature schemes without a hard fork for each one. A separate A-tier package, EIP-8298 and EIP-8151, completes the route by letting accounts abandon secp256k1 as the master key. A third, EIP-8365, begins retiring validator withdrawal credentials still tied to weak cryptography.

The consensus layer receives the opposite treatment. Its cryptography cannot be swapped without a fork, so components wait for the complete design. Hash-Chain RANDAO landed at B tier, sound in direction but early in sequence.

The caution extends to the execution layer. ML-DSA verification precompiles fell to C tier, with the cluster declining to standardize one scheme before a dedicated cryptographic review.