
The Ethereum Foundation has put a date on a problem the network cannot date: it wants Ethereum’s base layer to be resistant to attacks from quantum computers across execution, consensus and data by December 2029.
The commitment, published by the Foundation’s Protocol cluster on September 7, turns post-quantum cryptography from a distant research subject into a constraint on the next several network upgrades. It does not mean quantum computers can break Ethereum today, and it does not predict that such a machine will arrive in 2030. The Foundation is planning against an uncertain threat before migration becomes urgent.
A deadline built around uncertainty
The Protocol cluster calls its 2029 target deliberately aggressive. Its working assumption is that a cryptographically relevant “Q-day” could arrive as early as 2030, while acknowledging that many estimates place it later and that it may never arrive at all. The practical choice is between starting a long migration early or betting that operators, wallets and validators can move quickly after the threat becomes clearer.
Ethereum cannot solve that migration with one software patch. Current accounts and validator credentials depend on cryptographic schemes that a sufficiently capable quantum computer could threaten. The network’s execution, consensus and data layers also have different requirements. Account signatures may become more flexible; consensus cryptography, which coordinates validators and finality, must be changed through hard forks and tested as a system.
That is why the 2029 target matters even without a firm forecast for quantum hardware. It creates a planning horizon for protocol designers, client teams and security reviewers. It also exposes the schedule risk: the Foundation’s roadmap places full readiness several forks after Glamsterdam, requiring overlapping research and implementation rather than a simple upgrade-by-upgrade sequence.
Hegotá is the first scheduling test
The next fork being scoped, Hegotá, is not described as Ethereum’s post-quantum upgrade. Its role is more indirect. The Foundation argues that choices made now will determine whether later post-quantum milestones remain achievable.

Two proposals sit at the center of that scope. EIP-7805, known as FOCIL, would let a committee of validators publish transaction inclusion lists. Attesters would withhold votes from blocks that omit eligible listed transactions, subject to validity and block-space limits. The design aims to reduce the censorship power that can arise when block construction is concentrated among specialized builders.
EIP-8141, Frame Transactions, would separate transaction validation, gas payment and execution into programmable frames. Among its intended benefits are native key rotation, batching and support for alternative signature schemes. That cryptographic flexibility is central to moving user accounts away from today’s vulnerable master-key assumptions without requiring a new hard fork for every future signature scheme.
Both EIPs remain drafts. Their selection as top priorities signals engineering attention, not completed deployment. The Protocol cluster’s published tier list evaluated 62 candidate EIPs and placed FOCIL and Frame Transactions in its highest tier, while warning that integration depth and testing capacity are the scarce resources.
The trade-off is scope, not ambition
A roadmap this broad invites a familiar failure mode: every desirable improvement competes for the same client developers, researchers and test networks. The Foundation’s answer is to keep Hegotá’s consensus-layer scope tight and make additional work justify the delay it could impose on the post-quantum path.
That discipline has consequences. Proposals can be technically sound and still fall below the line because they add testing surface or depend on designs that are not mature. The published process moves work through research, an Ethereum Improvement Proposal, prototypes, development networks and progressively stronger inclusion signals before mainnet. An item can move backward when evidence reveals a problem.
There is also a technical tension inside FOCIL itself. Inclusion lists strengthen transaction inclusion guarantees, but block builders must receive and process the lists in time. The draft’s security section recognizes that builders need reliable connectivity to committee members and enough time to assemble a compliant payload. Censorship resistance gains are therefore tied to careful timing, bandwidth limits and implementation work.
What users and operators should watch
Nothing in the announcement requires an ETH holder to change keys today. Wallets, exchanges and staking operators should instead watch for three types of evidence: stable specifications, working multi-client prototypes and migration tools that ordinary users can operate safely.
For validators, the retirement path for older withdrawal credentials will matter as the consensus design develops. For wallet teams, Frame Transactions could change how accounts authorize actions and pay fees. For application developers, the immediate issue is compatibility: transaction handling, simulation and infrastructure must recognize new transaction types before they reach mainnet.
The December 2029 date is a commitment by one major coordinating group, not a guarantee that every dependency will ship on schedule. The credible measure of progress will be narrower than the headline—specifications that stop changing, interoperable client implementations, adversarial testing and a migration path that does not strand users.
Primary sources: Ethereum Foundation, “EF Protocol: Current and Emerging Priorities” and the Hegotá EIP tier list, both published September 7, 2026; official draft specifications for EIP-7805 and EIP-8141. Sources checked September 11, 2026.
Investment disclaimer: This article is provided for general information only and does not constitute investment, financial, legal or tax advice. Digital assets are volatile, and all investment decisions and their consequences are your own responsibility.