TLDR
- The Ethereum Foundation named two “must ship” proposals for the Hegotá upgrade: FOCIL and Frame Transactions
- FOCIL strengthens censorship resistance by letting validator committees force transaction inclusion
- Frame Transactions brings native account abstraction and post-quantum authentication to Ethereum
- The Foundation evaluated 62 EIPs with input from around 60 researchers and engineers
- Ethereum is targeting full post-quantum security across all layers by December 2029
The Ethereum Foundation has named two proposals as essential for its upcoming Hegotá upgrade. The two “must ship” items are FOCIL and Frame Transactions, which will define the fork’s scope and schedule.
Ethereum Foundation Grades 62 Hegotá EIPs, Targets Quantum-Resistant L1 by 2029
The Ethereum Foundation’s Protocol Cluster published its Hegotá upgrade assessment and roadmap, grading 62 proposed EIPs. EIP-7805 (FOCIL, an anti-censorship proposal) and EIP-8141 (Frame… pic.twitter.com/rE2xoI9j5D
— Wu Blockchain (@WuBlockchain) September 7, 2026
The Foundation’s Protocol cluster evaluated 62 Ethereum Improvement Proposals, drawing on input from about 60 researchers and engineers. This is the first time the Protocol cluster has published a single unified ranking instead of separate opinions from individual teams.
What FOCIL and Frame Transactions Do
FOCIL, formally known as EIP-7805, targets censorship resistance. It would allow a validator committee to force the inclusion of valid transactions from the public mempool, preventing dominant block builders from blocking them.
LATEST: ⚡️ The Ethereum Foundation's Protocol cluster published a tier list grading 62 EIPs proposed for the Hegotá fork, naming FOCIL and Frame Transactions as S-tier. pic.twitter.com/emkBFn2SIL
— CoinMarketCap (@CoinMarketCap) September 8, 2026
Frame Transactions, or EIP-8141, brings native account abstraction to Ethereum. It splits transactions into programmable parts for validation, gas payment, and execution, allowing wallets to use custom signatures and batched actions without relying on off-chain operators.
Together, the two proposals form what the Foundation calls the “core engineering commitment” of the Hegotá upgrade. If either is at risk of being cut, the upgrade schedule will be adjusted rather than dropping the proposal.
Beyond the two headliners, 15 proposals landed in the A-tier, meaning they are expected to ship unless development constraints force cuts. Eight more are candidates, seven are below the line but not ruled out, and 28 were declined for inclusion.
Ethereum’s 2029 Quantum Security Target
The Foundation also published a broader priorities post alongside the Hegotá rankings. Its stated “north star” is making Ethereum fully quantum resistant across execution, consensus, and data layers by December 2029.
That target aligns with migration timelines from Google, Cloudflare, and Microsoft. The Foundation said it is treating 2029 as a firm deadline, at least until January 2027 when quantum progress will be reassessed with outside experts.
The Foundation noted that most credible estimates place a quantum computing threat, referred to as “Q-day,” later than 2030. But it chose to set an aggressive internal deadline rather than wait for certainty.
Hegotá is not itself the post-quantum fork. It is the upgrade that keeps future post-quantum forks on schedule.
Reaching the December 2029 target from Glamsterdam, expected in late 2026, would require an average pace of 7.2 months per fork. The Foundation acknowledged there is little room for error in that timeline.
Two EIPs remain unranked until mainnet data from Glamsterdam is available. Client teams could begin implementing Hegotá in late 2026 once Glamsterdam is complete.
Ethereum’s last major upgrade, Fusaka, went live on December 3, 2025. Its headline feature changed how nodes handle rollup data, reducing bandwidth requirements while increasing data capacity for layer-2 networks.
Post-quantum readiness is one of five multi-fork research arcs for the Ethereum protocol, alongside fast finality, privacy, state, and zkEVM.
