I still remember the quiet tension in the last All Core Developers call. Someone joked that sixty-six proposals felt less like a roadmap and more like a crowded airport lounge. Everyone wanted a seat on the 2027 flight called Hegotá, yet the gate agents (the client teams) were already checking boarding passes with sharper eyes than usual. That is exactly where Ethereum sits right now. The network’s next major upgrade after Glamsterdam is being ruthlessly scoped, and the process feels both methodical and strangely human.
Why Hegotá Matters More Than Most People Realize
Glamsterdam is still on track for the final quarter of 2026. Hegotá is penciled in for sometime the following year. On paper that sounds distant. In practice the decisions being made this August and September will lock in the technical DNA of Ethereum for half a decade. Censorship resistance, native account abstraction, privacy tooling, gas economics and validator incentives are all on the chopping block. Only one feature has already received the green light for inclusion. Everything else is fighting for oxygen.
I have watched enough protocol upgrades to know that early enthusiasm often collapses under implementation weight. Hegotá is following that familiar pattern, except the stakes feel higher this time. Block production has grown more specialized. Privacy research has accelerated. Gas limits keep climbing. If the wrong combination of EIPs lands (or fails to land), the network could end up with half-measures that satisfy no one.
FOCIL Stands Alone as the Only Scheduled Feature
EIP-7805, better known as Fork Choice enforced Inclusion Lists, or FOCIL, is currently the sole item marked for inclusion. The idea is straightforward on the surface and elegant underneath. A rotating committee of validators publishes transaction inclusion lists. Block builders are expected to honor those lists. Attesters refuse blocks that improperly leave eligible transactions on the cutting-room floor. The goal is simple: make it much harder for a handful of sophisticated builders to systematically exclude transactions they dislike.
In my view this is the most important single change Hegotá can deliver. Specialization in block construction has brought efficiency, but it has also concentrated power. FOCIL does not pretend to eliminate that concentration. It simply adds a credible enforcement layer so that censorship becomes expensive and visible. Privacy researchers have quietly noted that stronger inclusion guarantees also protect transactions that carry more sensitive payload data. That secondary benefit should not be underestimated.
FOCIL is already Hegotá’s main scheduled feature and the only one that currently enjoys formal inclusion status.
The design still needs careful parameterization. Committee size, list length, and the exact conditions under which attesters reject a block remain open questions. Yet the core mechanism has survived multiple rounds of scrutiny. That alone puts it in a different category from the rest of the proposal pile.
Frame Transactions and the Account Abstraction Debate
Native account abstraction refuses to settle quietly. Two competing approaches currently dominate the conversation. EIP-8141 introduces Frame Transactions. The concept allows validation logic, execution logic and gas payment to be defined through programmable frames rather than the rigid ECDSA-plus-nonce model that has governed Ethereum since day one. Supporters argue this opens the door to alternative signature schemes, seamless key rotation, gas sponsorship and a cleaner path toward privacy-preserving authentication.
EIP-8130 offers a different technical route toward similar ends. Client teams agreed to put both proposals under the microscope during an August 25 breakout session, with a formal decision expected at the August 27 ACDE meeting. That is an unusually tight timeline. I have seen less contentious EIPs take months to resolve. The pressure is intentional. Account abstraction has been discussed for years. Hegotá is the moment when the network either commits or continues the familiar pattern of half-measures and external workarounds.
One researcher has publicly argued that Frame Transactions should travel together with FOCIL, keyed nonces and recent roots as part of a coherent native privacy stack. That remains an individual position rather than a core-developer consensus. Still, the logic is hard to dismiss. Privacy features that depend on weak inclusion guarantees or clumsy authentication layers tend to underperform in the real world. Bundling the right primitives could create compounding benefits that isolated upgrades never deliver.
Gas Repricing Proposals Aim at Safer Scaling
Several proposals focus on making larger blocks safer rather than simply bigger. EIP-8131 would impose a uniform floor of 64 gas for every user-controlled byte inside a transaction. EIP-8279 extends similar accounting to Block Access List data, closing a loophole that could otherwise let blocks swell beyond intended size as the gas limit rises. EIP-8368 goes further. It proposes recalibrating state-creation pricing once the block gas limit moves past the reference level assumed by Glamsterdam.
Glamsterdam itself is currently targeting roughly 200 million gas. Some developers have spoken openly about a longer-term path toward 600 million. That kind of jump is only responsible if the pricing model for state growth keeps pace. Leaving the old parameters in place while the gas limit climbs is a recipe for state bloat that later generations of node operators will have to live with. I find the caution around EIP-8368 healthy. The draft still contains unspecified parameters, which is exactly the right posture when the numbers will shape the economics of storage for years.
In practice these gas-repricing EIPs feel less glamorous than FOCIL or Frame Transactions. They also feel more necessary. Scaling without corresponding cost adjustments has burned other networks. Ethereum has the institutional memory to avoid that particular trap, provided the client teams keep the pressure on.
The September Deadline and Preference Lists
Core developers have set a clear calendar. The proposed-for-inclusion list for Hegotá should be finalized by late August. Any proposal lacking an active champion can be dropped without ceremony. Execution client teams must then submit ranked preference lists by September 10. Those ranked lists will heavily influence which ideas receive implementation attention, public devnets and eventually mainnet consideration.
This process is more disciplined than some earlier upgrade cycles. I remember upgrades where popular ideas lingered on the board long after their technical readiness had stalled. The current approach forces accountability. If a proposal cannot attract a champion and a client-team ranking, it simply exits the conversation. That is harsh. It is also the only way a network of this size can ship meaningful change on a predictable schedule.
Other ideas remain in the broader discussion even if their formal status is weaker. Eight-second slots under EIP-8198, anti-correlation penalties for validators under EIP-7716, post-quantum cryptography experiments and adjustments to ETH issuance all surface periodically. None of them currently enjoy scheduled status. EIP-8198 is still a draft. EIP-7716 is marked stagnant despite appearing on some Hegotá proposal trackers. The next few developer calls will determine whether any of these regain momentum or quietly fade.
Privacy as a Cross-Cutting Concern
One of the more interesting undercurrents is how privacy considerations keep attaching themselves to otherwise separate proposals. FOCIL strengthens inclusion guarantees that privacy-preserving transactions desperately need. Frame Transactions could reduce reliance on ECDSA signatures that are easier to link across time. Recent-roots and keyed-nonce ideas further reduce the metadata leakage that currently makes sophisticated analysis possible.
I am not suggesting Hegotá will suddenly turn Ethereum into a privacy chain. That is neither the design goal nor a realistic near-term outcome. What I am noticing is a quiet alignment among researchers who care about both censorship resistance and privacy. The same mechanisms that make it harder to exclude transactions also make it harder to selectively surveil them. That dual benefit is worth protecting during the ruthless prioritization that is about to intensify.
What Client Teams Actually Care About
Client diversity remains one of Ethereum’s quiet strengths. It is also a constraint. An EIP that looks elegant on a whiteboard can become a multi-month engineering slog once five independent client teams have to implement, test and maintain it. Preference lists submitted in September will therefore reflect real resource calculations rather than pure technical elegance.
Teams will weigh implementation complexity, interaction risks with existing code, testing burden and long-term maintenance cost. Features that deliver clear user value with manageable engineering overhead will rank higher. Features that require extensive new cryptography or deep changes to the consensus layer will face steeper scrutiny. That filtering process is healthy even when it disappoints individual proposal authors.
In my experience the best upgrades are those that feel slightly under-scoped on the day they ship. They leave room for the next cycle rather than trying to solve every open problem at once. Hegotá appears to be moving in that direction. The early presence of sixty-six proposals was never meant to survive. The point of the current process is to reduce that number to a coherent, implementable set.
The Broader Roadmap Context
Hegotá does not exist in isolation. Glamsterdam is already testing major Layer-1 scaling changes, including block-level access lists and extensive gas repricing. Those changes will shape the baseline that Hegotá inherits. If Glamsterdam successfully raises the gas limit and stabilizes the new pricing model, Hegotá can focus more attention on inclusion guarantees and account abstraction. If Glamsterdam encounters unexpected friction, Hegotá may need to absorb additional scaling work.
That interdependency is why the September preference lists matter so much. Client teams are not ranking Hegotá proposals in a vacuum. They are ranking them against the residual work that Glamsterdam may leave behind and against the long-term research agenda that already includes post-quantum considerations and further state-growth management.
Perhaps the most interesting aspect is how little of this process is visible to casual observers. Most public conversation still treats upgrades as singular events rather than multi-year pipelines of prioritization, implementation and cleanup. The real work happens in the unglamorous weeks of ranking, championing and hard trade-offs. Hegotá is currently living inside those weeks.
Potential Risks of Over-Scoping
Every upgrade cycle carries the temptation to include “just one more” feature. The cost of that temptation is rarely paid immediately. It appears later as delayed shipping, diluted testing, or subtle interactions that only surface under mainnet load. The current narrowing process is therefore more important than any individual EIP.
I have found that networks which ship focused upgrades tend to maintain higher confidence among both users and developers. Networks that try to solve every problem in a single hard fork often create the impression of perpetual unfinished business. Ethereum has largely avoided the second pattern in recent years. The Hegotá scoping exercise looks designed to keep that record intact.
There is also a subtler risk. If too many privacy or account-abstraction ideas are deferred, external solutions will continue to fill the gap. Some of those external solutions are excellent. Others introduce their own trust assumptions and complexity. A native path, even if modest, reduces reliance on the external layer. That is one reason the Frame Transactions discussion deserves careful attention even if it ultimately does not make the final cut.
How the Community Can Follow the Process
Most of the decisive conversations happen in All Core Developers Execution calls and the associated breakout sessions. Summaries appear afterward, yet the real texture lives in the live discussion. Preference lists submitted by client teams in September will offer the clearest public signal of which proposals still have momentum.
Observers who care about specific features should treat the next three weeks as the critical window. After September 10 the conversation shifts from “should this be considered” to “can this be implemented and tested in time.” That shift is decisive. Ideas that lack ranked support at that point face a steep climb back into contention.
I expect the final Hegotá scope to look smaller and tighter than the current proposal landscape. FOCIL will almost certainly remain. A limited form of account abstraction may survive if the August 27 decision is favorable and client teams rank it highly. Gas-repricing work that supports safer scaling has a realistic chance. Everything else will need an unusually strong champion and clean engineering path.
Looking Past 2027
Even after Hegotá ships, the deeper research questions will remain. Post-quantum cryptography is not going away. State growth will continue to demand attention. Validator economics will keep evolving as the set of participants changes. Hegotá is best understood as one solid step rather than a final settlement of these issues.
That perspective is oddly liberating. It reduces the pressure to solve every problem inside a single upgrade and increases the pressure to solve the chosen problems well. The current narrowing process, uncomfortable as it feels for proposal authors, is the practical expression of that philosophy.
Ethereum has grown large enough that its upgrade process must balance ambition with realism. The sixty-six proposals that entered the Hegotá conversation represented ambition. The ranked lists that will emerge in September will represent realism. The tension between those two forces is where the network’s long-term health is decided.
For anyone watching the protocol evolve, the next month of developer calls will be more revealing than most mainnet launches. The features that survive will shape how Ethereum handles censorship resistance, privacy and scaling through the late 2020s. The features that fall away will wait for a later cycle or find new homes outside the core protocol. Either outcome is preferable to an overloaded upgrade that ships late and under-tested. The current process, for all its friction, is designed to avoid that particular failure mode. That is worth paying attention to.
I keep returning to the airport-lounge image. Sixty-six passengers showed up hoping for a seat. The gate is closing. Only a handful will board the 2027 flight. The rest will rebook for later. The network will be better for the discipline.
