Something quietly shifted in the Ethereum development conversation this week. A research group called Ethlabs released a detailed paper outlining exactly which features it believes should sit at the top of the list for the Hegota upgrade. If you follow protocol discussions even casually, you already know Hegota is the planned hard fork that comes after Glamsterdam, currently expected sometime in 2027. What makes this particular paper interesting is not just the recommendations themselves, but the clear ranking and the reasoning behind each choice.
I’ve been watching these scoping processes for a while, and they rarely feel this focused this early. Most of the time developers throw a long list of EIPs into the mix and spend months sorting them. Here, Ethlabs has already done a lot of that sorting for anyone willing to listen. The group places four priorities above everything else: censorship resistance through FOCIL, faster block times via Quick Slots, a practical path to native account abstraction with Frame Transactions, and continued Layer 1 scaling through carefully designed data-repricing proposals. The rest of this piece walks through each of those points, what they actually mean for users and developers, and why the timing of these decisions matters more than it might appear at first glance.
Why Hegota Matters More Than Another Ordinary Upgrade
Ethereum has already shipped several major upgrades in the past few years. The Merge, Shanghai, Dencun, and the upcoming Glamsterdam have each changed the network in measurable ways. Hegota sits further down the roadmap, yet the decisions made now will shape the network’s capabilities for years. Slot times, transaction flexibility, and how the protocol handles data growth are not small technical details. They directly influence user experience, application design, and the long-term economic model of the chain.
Ethlabs is careful to describe its paper as a recommendation rather than an official governance decision. That distinction is important. The official Hegota meta currently lists only one feature as scheduled for inclusion: EIP-7805, better known as FOCIL. Everything else remains under discussion. Frame Transactions have moved into the “considered for inclusion” category, which is a meaningful step, but still not a guarantee. Dozens of other proposals sit in various stages of readiness. Execution client teams have until September 10 to submit their own rankings. After that, the circle of serious candidates will almost certainly shrink.
In my view, the value of the Ethlabs document is that it forces a clearer conversation. Instead of treating every EIP as equal, the group draws a sharp line between must-haves and nice-to-haves. That kind of prioritization is rare and useful.
FOCIL: Keeping Censorship Resistance Front and Center
FOCIL stands for Forced Inclusion Lists. At its core, the idea is simple. Validators create inclusion lists that force block builders to include certain valid transactions. Specialized builders who might otherwise omit transactions for economic or political reasons become less able to do so. Attesters only support blocks that satisfy the relevant inclusion-list conditions. The result is a stronger guarantee that the network remains neutral about which transactions get processed.
Ethlabs ranks this feature at the very top of its priorities, and for good reason. Censorship resistance has always been one of Ethereum’s selling points. In practice, the rise of sophisticated block builders and private transaction flows has created new pressure points. FOCIL does not solve every problem, but it raises the cost of selective exclusion in a way that feels native to the protocol rather than bolted on later.
The proposal already holds the official headliner position for Hegota. That status is not accidental. Developers have been discussing versions of inclusion lists for a long time. The current design appears mature enough that most client teams treat it as a baseline rather than an optional experiment. Still, implementation details matter. How the lists are constructed, how often they refresh, and how they interact with existing proposer-builder separation mechanics will determine whether the feature delivers the intended protection without creating new bottlenecks.
I’ve found that conversations about censorship resistance sometimes stay abstract. People talk about principles without grounding them in the actual mechanics of block production. FOCIL is concrete. It changes the rules of what a valid block can look like. That concreteness is why it deserves the attention it is receiving.
QuickSlots and the Push for Faster Blocks
The second priority on Ethlabs’ list is EIP-8198, known as QuickSlots. Ethereum currently operates with twelve-second slots. The proposal suggests beginning the process of reducing that interval during Hegota. Eight seconds appears as a placeholder target in the current draft, though Ethlabs itself talks about the possibility of landing around ten seconds within roughly a year of the upgrade. The exact number remains open and will depend on testing and client readiness.
Faster slots sound straightforward until you start thinking about the downstream effects. Shorter slots mean shorter epochs if the number of slots per epoch stays fixed at thirty-two. That shortens the time to finality. It also increases the number of blocks produced in a given period, which raises bandwidth and processing demands on nodes. The network has to stay decentralized while becoming more responsive. Those two goals do not always pull in the same direction.
Ethlabs argues that starting the reduction during Hegota is important. Waiting for a later fork risks leaving Ethereum feeling slow relative to newer chains that already advertise sub-second finality. Of course, sub-second finality is a different design space entirely. Ethereum’s strength has always been careful engineering rather than racing to the lowest latency number. Still, twelve seconds is long enough that users notice the wait when they interact with applications that feel more responsive elsewhere.
Perhaps the most interesting aspect of the QuickSlots discussion is how it interacts with other scaling work. If gas limits continue to rise and data throughput improves, the network will produce more data per unit of time. Faster slots amplify that effect. Coordinating these changes so that one does not break the other requires the kind of careful sequencing that Hegota scoping is supposed to provide.
Frame Transactions as a Path to Native Account Abstraction
Account abstraction has been a recurring theme in Ethereum discussions for years. The idea is to let accounts define their own validation and gas-payment logic instead of being locked into the traditional externally owned account model. Several approaches have been proposed. Ethlabs prefers EIP-8141, Frame Transactions, and ranks it in its second-highest priority tier.
Frame Transactions allow transaction validation and gas payment to be controlled through EVM code. That opens the door to several practical improvements. Users could authenticate with passkeys. Applications could sponsor gas fees. Transactions could be batched more cleanly. Alternative signature schemes, including those designed with post-quantum considerations in mind, become easier to introduce. Gas payments denominated in tokens other than ETH also become more natural.
Officially, Frame Transactions now sit in the “considered for inclusion” category. That is stronger standing than most Hegota candidates enjoy. Inclusion is still not guaranteed. Competing designs continue to circulate, and developers will need to decide which approach best balances flexibility, security, and implementation cost. From the outside, the progress of Frame Transactions feels like a genuine step toward making account abstraction a native protocol feature rather than something layered on through smart contracts and specialized infrastructure.
In my experience, users rarely care about the underlying mechanism. They care about whether they can pay gas in the token they already hold, whether they can recover an account without a seed phrase, and whether complex interactions can be expressed in a single transaction. Frame Transactions aim to make those experiences feel ordinary rather than experimental. That is a worthwhile goal.
Data Repricing and Safer Gas Limit Increases
The fourth priority cluster centers on two related proposals: EIP-8131 and EIP-8279. Both address how the protocol accounts for the data that transactions and blocks produce. EIP-8131 introduces a uniform sixty-four gas floor for user-controlled transaction bytes. The specification estimates that even at a sixty-million gas limit, the worst-case content size stays around 0.89 megabytes. Fewer than four percent of sampled mainnet transactions would hit the new floor under current conditions.
EIP-8279 extends similar accounting to Block Access List bytes created during execution. Together, the two proposals close gaps in bandwidth accounting that could otherwise limit how far gas limits can safely rise. Higher gas limits are one of the most direct ways to increase Layer 1 capacity. Without better data accounting, those increases risk creating situations where a single block becomes too large for many nodes to process comfortably.
Ethlabs places both proposals in its top tier. Neither is currently scheduled for Hegota, so their inclusion remains uncertain. The reasoning behind the ranking is straightforward. Scaling Layer 1 remains essential even as Layer 2 solutions continue to mature. Users and applications still settle important activity on the base layer. Keeping that layer capable of handling more activity without sacrificing decentralization is a core responsibility of protocol development.
One practical observation: gas-limit discussions often become heated because they touch on node requirements and centralization risks. Repricing proposals that make the relationship between gas and actual resource usage more accurate tend to lower the temperature of those debates. They give developers a clearer basis for deciding how far limits can move.
What Ethlabs Chose Not to Rank
The paper is notable for what it leaves out as much as for what it includes. Ethlabs declined to rank EIP-8363, a proposal that would change issuance by burning a rising share of validator rewards as the staking ratio increases. The group’s position is that monetary policy questions deserve broader community debate rather than being treated as ordinary technical scoping decisions. That stance feels measured. Issuance changes affect every stakeholder, and the process for deciding them should reflect that breadth.
Other proposals remain in the larger pool of candidates. Some will advance. Others will wait for later forks or fade away. The September 10 deadline for client rankings will clarify the picture considerably. After that, the conversation will shift from long lists of possibilities to a shorter list of features that teams are prepared to implement and test.
How the Official Process Is Unfolding
Ethereum’s upgrade process has become more structured over time. Meta EIPs track the status of features for each fork. Client teams provide independent assessments of feasibility and priority. Researchers and independent groups publish analyses that feed into the discussion. Ethlabs occupies one of those independent seats. Its paper does not bind anyone, yet it adds a coherent voice at a moment when coherence is useful.
The current official status is clear enough. FOCIL is scheduled. Frame Transactions are considered for inclusion. Everything else is still competing for attention and resources. That ranking can change as more technical analysis appears and as client teams submit their own views. The process is designed to be iterative precisely because early rankings sometimes miss important interactions between proposals.
Looking ahead, Hegota is still more than a year away under the current roadmap. That distance is both a challenge and an opportunity. It leaves room for thorough testing and for second thoughts. It also creates the risk that momentum dissipates and that important improvements slip further into the future. Ethlabs’ decision to publish a clear set of priorities helps keep the conversation concrete during that long window.
Practical Implications for Users and Builders
What does any of this mean if you are not a core developer? Faster slots would make the network feel more responsive. Native account abstraction features would make wallets and applications more flexible and, in many cases, more secure. Better data accounting would support higher capacity without forcing every node operator to upgrade hardware at the same moment. Stronger censorship resistance would preserve the neutrality that many users value about Ethereum.
None of these improvements will arrive overnight. Even after inclusion decisions are finalized, client implementation, testing, and the actual hard-fork activation take time. Still, the direction of travel is becoming clearer. Ethereum is not standing still while other chains experiment with different trade-offs. It is refining its own path with a focus on properties that have defined the network from the beginning.
I’ve noticed that some observers treat every upgrade cycle as either a breakthrough or a disappointment. The reality is usually quieter. Each fork removes specific friction points and raises the ceiling on what the network can do. Hegota looks likely to continue that pattern. The four priorities highlighted by Ethlabs form a coherent package: protect neutrality, improve responsiveness, expand what accounts can do, and keep capacity growing in a controlled way.
Looking Past the Immediate Ranking Exercise
The September 10 deadline will produce a new set of signals. Client teams will reveal which proposals they consider ready and which they believe need more work. Those rankings will not be identical to Ethlabs’ list, and that is healthy. Different teams bring different constraints and different experiences with earlier upgrades. The eventual feature set will reflect a negotiation among those perspectives.
One open question is how much weight will be given to user-facing improvements versus pure protocol hardening. FOCIL and data-repricing proposals lean toward the latter. QuickSlots and Frame Transactions lean toward the former. Balancing those two categories is part of the art of scoping a major fork. Too much focus on internal robustness can leave the network feeling stagnant to users. Too much focus on visible features can introduce complexity that later becomes difficult to manage.
Ethlabs has drawn a line that tries to capture both sides. Whether the broader developer community draws the same line remains to be seen. The paper at least gives everyone a clear reference point for the discussion.
A Quiet but Meaningful Moment in the Roadmap
Roadmap documents and research papers rarely make headlines outside specialist circles. This one probably will not either. Yet the choices being debated now will determine how Ethereum feels to use in 2027 and beyond. Slot times measured in seconds, accounts that can define their own rules, blocks that remain resistant to selective exclusion, and a base layer that continues to scale without losing its decentralized character are not minor details. They are the practical expression of the values the network has claimed since its earliest days.
Ethlabs has done the useful work of ranking those values against the concrete proposals on the table. The rest of the process will test whether that ranking holds or whether new information shifts the priorities. Either outcome is fine. What matters is that the conversation stays focused on the properties that actually matter to the long-term health of the network.
For now, FOCIL remains the only scheduled feature. Frame Transactions have moved closer to the center of the discussion. QuickSlots and the data-repricing proposals sit high on at least one independent research group’s list. The next few months of rankings and technical review will decide how much of that preferred package becomes part of Hegota itself. Until then, the paper serves as a useful map of one coherent vision for where Ethereum should go next.
The upgrade will not solve every open question. No single fork ever does. But if the priorities outlined here survive the scoping process in something close to their current form, Hegota will leave the network more resistant to censorship, more responsive, more flexible for account design, and better prepared for higher capacity. Those are outcomes worth watching carefully as the formal decision process continues.
