The Ethereum Foundation Protocol cluster published its priorities framework on September 7, setting a December 2029 deadline for Ethereum L1 to achieve quantum resistance across all three layers: execution, consensus, and data. The post named the upcoming Hegotá upgrade as the fork that determines whether the entire post-quantum schedule holds, not the fork that delivers quantum resistance itself.
"Shipping post-quantum readiness early is the secure thing to do. It is the strategically responsible thing to do," the Protocol cluster wrote. "It is the clearest signal we can send that Ethereum intends to exist 50, 100, and 1,000 years from now."
The December 2029 target aligns with independent migration deadlines set by Google, Cloudflare, and Microsoft. The Protocol cluster acknowledged that most credible estimates place a cryptographically relevant quantum computer, referred to as Q-day, later than 2030, and that it may never arrive. The deadline is self-imposed and deliberate.
"Its timing is outside anyone's control, which is exactly why we have fixed a target rather than waiting for certainty," the post said.
The deadline will be treated as non-negotiable at least until January 2027, when quantum progress will be reassessed with outside experts.
What Hegotá must deliver and why the fork order matters
Glamsterdam is due to ship in December 2026. Reaching the minimum viable post-quantum milestone at the fork labeled J* by December 2029 requires an average cadence of 7.2 months per fork. The Protocol cluster described that pace as aggressive with little room for slippage. To meet it, forks will run in parallel rather than sequentially, with Hegotá shipping while specifications for I* mature and research for J* through L* progresses simultaneously.
Hegotá has two S-tier, must-ship headliners. On the consensus layer, FOCIL, formally EIP-7805, Fork-choice Enforced Inclusion Lists, would allow a validator committee to force inclusion of valid public-mempool transactions, preventing a dominant block builder from censoring them. On the execution layer, Frame Transactions, EIP-8141, makes account abstraction native to Ethereum by splitting a transaction into programmable frames for validation, gas payment, and execution.
"Delivering both headliners safely, and testing the interaction between them, is the fork's core engineering commitment," the Protocol cluster wrote.
What Frame Transactions actually fixes for ordinary users
The practical problem Frame Transactions addresses is straightforward. A wallet can hold hundreds of dollars in stablecoins and be unable to move them because Ethereum charges fees in ether and a wallet without ether cannot pay. EIP-8141 separates the account sending funds from the account paying the fee, which means a payments application could cover the fee itself, or accept stablecoins from the user and settle the ETH cost on their behalf.
Core developers moved EIP-8141 to Scheduled for Inclusion at their August 27 call. Ethereum co-founder Vitalik Buterin, one of the proposal's ten authors, wrote on X that "a lot of important progress on Frames (EIP-8141) has been quietly happening over the last few months."
A lot of important progress on Frames (EIP-8141) has been quietly happening over the last few months. Highly recommend reading this, also the updated EIP https://t.co/jYqeS55j6P
— vitalik.eth (@VitalikButerin) September 5, 2026
https://t.co/CPYONKnWZc
Frame Transactions also addresses a security problem that predates quantum computing. Every standard Ethereum account is controlled by a single secp256k1 private key. That key cannot be rotated or replaced without moving funds to a new address. If a key is compromised, there is no protocol-level mechanism to revoke it. Frame Transactions provides a native route for accounts to move away from secp256k1 keys and adopt new signature schemes without requiring a separate hard fork for each scheme. That property is what the Protocol cluster calls cryptographic agility, and it is the execution layer's primary defense against quantum threats because the consensus layer cannot use the same approach and must instead wait for a complete post-quantum design before any consensus cryptography changes.
The Frames-extension package in Hegotá includes EIP-8298, which lets delegated accounts become full smart-contract accounts, and EIP-8151, which blocks legacy key authentication once an account has real code. Together they create a migration path away from secp256k1 as a master key at the account level.
The five research arcs running in parallel through 2029
Beyond the immediate Hegotá delivery, the Protocol cluster organizes its longer-horizon work into five multi-fork arcs. Fast finality targets reducing Ethereum's time to finality from minutes to seconds through decoupled consensus, with I* as the leading candidate for that headliner. The post-quantum arc spans all three layers and drives the December 2029 deadline. The privacy arc aims to make private transactions a protocol guarantee rather than a third-party service, with work beginning in Hegotá through Keyed Nonces and Recent Roots. The state arc addresses trie migration and sustainable state growth. The zkEVM arc moves execution proofs from optional to mandatory, currently targeted at K* under the existing Strawmap, though a reordering that would swap mandatory proofs and post-quantum attestations is under review.
The zkEVM arc represents one of the most structurally significant changes in Ethereum's history. Today, every validator re-executes every transaction to verify block validity. Under a zkEVM model, validators instead verify a succinct zero-knowledge proof that all transactions in a block were executed correctly, without re-executing them. This reduces the computational burden on validators and enables a class of validity guarantees that re-execution cannot provide. Ethereum researchers have debated the zkEVM roadmap since at least 2021, when Buterin outlined the endgame vision. The Protocol cluster's placement of mandatory proofs in K with a possible move to L reflects ongoing uncertainty about proving time and client implementation complexity rather than disagreement about the destination.
The Protocol cluster is hosting a Reddit AMA on r/ethereum on September 16 at 2 p.m. UTC to discuss the priorities and the Hegotá tier list. Questions can be submitted in advance through a linked form.
Gunel Ismayilova
Disclaimer: All materials on this site are for informational purposes only. None of the material should be interpreted as investment advice. Please note that, despite the nature of much of the material created and hosted on this website, HODL FM operates as a media and informational platform, not a provider of financial advisory services. The opinions of authors and other contributors are their own and should not be taken as financial advice. If you require advice, HODL FM strongly recommends contacting a qualified industry professional.
