The Ethereum Foundation (EF) Protocol cluster has officially published its first-ever unified tier list for the upcoming Hegoté network upgrade. In a departure from previous practices where individual engineering and research teams published fragmented, team-specific opinions, the cluster has consolidated its evaluations into a single cohesive document. Approximately 60 contributors spanning research and engineering across nine teams, alongside external domain experts, collaborated to build the comprehensive index. While execution layer client Geth will still release its own standalone tier list, its team members actively participated in the cluster-wide sessions, ensuring that their feedback and insights were woven directly into this overarching datapoint.
The newly released evaluation framework covers 62 Ethereum Improvement Proposals (EIPs) proposed for inclusion in the Hegoté fork. The scoring system assigns each proposal a specific tier alongside a concise rationale explaining the grade. To establish the foundational reasoning behind these evaluations, the cluster also released a companion document titled EF Protocol: Current and Emerging Priorities, outlining the strategic north star and overarching delivery plans that guided every decision.
I. How We Tiered
The collaborative effort behind the Hegoté tier list represents a major milestone in how the EF Protocol cluster coordinates protocol upgrades. Sixteen distinct contribution templates were submitted by the nine core teams and various individual specialists. Out of these submissions, 12 participants provided detailed tier grades. Recognizing the boundaries of specialization, several contributors chose to grade only those EIPs where they possessed deep, hands-on expertise.
In total, the process generated 397 individual tier grades across the 62 candidate proposals, resulting in an average of 6.4 grades per EIP, with the most heavily debated proposals drawing up to 9 independent grades. The cluster’s methodology was heavily shaped by lessons learned during retrospectives of the Glamsterdam upgrade. Key takeaways from those post-mortems included recognizing that EIP sizes should be measured by integration depth rather than surface simplicity, acknowledging that complexity compounds rapidly across client implementations, identifying the testing surface as a critically scarce resource, and noting that proposal champions routinely underestimate the true engineering complexity of their features.
To refine the initial data, the cluster engaged in half a dozen group conference calls and a rigorous 90-minute working session dedicated to ironing out contested items. Every contributor had originally tiered each EIP independently using a numerical scale where S equals 4 points, A equals 3, B equals 2, C equals 1, and D or DFI equals 0. Averages were calculated strictly using cast grades, meaning abstentions never penalized a proposal. Rather than simply publishing a raw mathematical average, the final tier list was constructed as a "steelman" argument. The grades served as a baseline, and every single EIP was debated individually during the working session, leading to upward and downward adjustments. To preserve collective candor, per-team grades are kept private, focusing public attention instead on the unified consensus.
Each tier on the scoring ladder establishes explicit delivery commitments for the cluster. For proposals expected to ship, the accompanying notes highlight their core merits. For proposals sitting on the bubble, the notes explicitly detail the precise requirements needed to secure an upgrade slot. For proposals placed below the line or formally declined, the notes outline the specific concerns that disqualified them without extraneous commentary.
II. The Tier List
The complete visual mapping of the tier list remains accessible via Forkcast, while the granular breakdown illustrates a clear bifurcation between essential protocol upgrades, highly debated structural experiments, and deferred initiatives.
Within the consensus layer, EIP-7805 (FOCIL) has emerged as an undisputed S-tier headliner. Achieving a unanimous S grade under full participation, FOCIL provides everyday users with a guaranteed path to include eligible transactions without depending on centralized block builders. It is slated to ship alongside EIP-8369, an A-tier proposal that defines transaction eligibility criteria for FOCIL and extends its robust inclusion guarantees directly to Frames.
Several other consensus layer proposals secured strong A-tier placements. EIP-8015, which cleanly removes dead deposit and eth1data fields with zero downstream dependencies, earned near-unanimous approval with an average score of 3.14. EIP-8365 starts the process of retiring withdrawal credentials tied to vulnerable cryptography, representing a vital post-quantum hygiene step that requires no waiting period. EIP-8383 reduces the consensus layer block retention window, correcting an earlier safety-decay constant. Meanwhile, EIP-8334 introduces bundled attestation propagation to reduce gossip load with minimal implementation surface, and EIP-8025 upstreams stateless execution changes directly into canonical execution specs to unify zkVM development.
Other consensus layer proposals landed in the B and C tiers, facing specific hurdles before they can be considered for inclusion. EIP-8146 (Block Access List Sidecars) has a strong case for the A tier once its observation deadline is formally settled in the specification. EIP-8237 explores independent consensus and execution layer synchronization to roughly halve sync bandwidth post-ePBS, though a simpler non-EIP alternative is currently being evaluated. EIP-8198 (Quick Slots) demonstrated strong theoretical support from research and development teams, but engineering teams rated it lower due to the cascading retuning required for slot-time changes. It requires comprehensive specifications, a working prototype, a downstream impact assessment, and decoupled consensus sign-off before advancing. EIP-8321 proposes a hash-chain RANDAO, but was placed in the B tier due to sequencing concerns regarding post-quantum consensus designs. Meanwhile, RowDAS (EIP-8371) sits in the C tier as a matter of operational priority rather than technical principle.
A substantial block of consensus layer proposals was designated as deferred or declined for Hegoté. These include EIP-7716 (Anti-Correlation Attestation Penalties), which requires further research regarding its impact on staker decentralization, and EIP-8367, EIP-8243, and EIP-8333, all of which intersect heavily with upcoming consensus redesigns or decoupled slot structures. Unanimously declined proposals in this category include block-in-blobs (EIP-8142), validator sweep thresholds (EIP-8148), withdrawal credentials preregistration (EIP-8205), beacon block reporting fields (EIP-8359), mandatory execution reward burns (EIP-8368 and EIP-8375), partial execution payload commitments (EIP-8341), and tapered issuance burns. Additionally, EIP-8368 and EIP-8372 remain in a TBD status, awaiting mainnet data and performance metrics from the Glamsterdam upgrade before any recalibration decisions can be made.
Turning to the execution layer, EIP-8141 (Frame Transactions) stands out as an S-tier headliner alongside consensus layer additions. Securing a near-unanimous average score of 3.89, Frame Transactions establish native account abstraction built on security foundations. They offer a unified path toward post-quantum signature schemes without necessitating separate forks for each scheme, introduce transaction aggregation to efficiently price post-quantum verification, and pave the way for retiring legacy k1 keys. Frame Transactions are designated to ship alongside EIP-8250 (Keyed Nonces) and EIP-8272 (Recent Roots).
A robust group of execution layer proposals claimed A-tier status. EIP-3298 removes refund mechanics to eliminate metering edge cases that plagued previous upgrades. EIP-5920 introduces the PAY opcode, enabling value transfers without invoking recipient code. EIP-8279 and EIP-8131 form a security-focused bounding pair that caps worst-case block construction and calldata content costs. EIP-7906 introduces transaction assertions via a state diff opcode to prevent wallet drains and MEV extraction, currently running alongside Frames on public devnets. EIP-8298 and EIP-8151 form the k1-retirement package, shifting 7702-delegated accounts into true smart contract accounts while disabling vulnerable ecRecover authentication paths. Finally, EIP-4758 achieves an A-tier placement by permanently deactivating SELFDESTRUCT, removing a persistent testing hazard for future EIPs based on direct advocacy from EVM maintenance engineers.
Several execution layer proposals landed in the B tier, including EIP-8253 to bump nonces of zero-nonce storage accounts, EIP-8077 for richer transaction announcements in the mempool, EIP-8374 and EIP-8358 for net-metering repricings, and EIP-7709 to read blockhashes from storage. The C tier contains cleanup and precompiled cryptography proposals such as receipt format changes (EIP-7668 and EIP-8116), EVMification of precompiles (EIP-8200 and EIP-7666), and premature post-quantum verification precompiles (EIP-8355).
A large contingent of execution layer changes was declined for the Hegoté fork. These include reserving extension opcodes (EIP-8163), adding new control-flow opcodes (EIP-7979), alternative account abstraction mechanisms like EIP-7851 and EIP-7819, linear memory costing repricings (EIP-7923 and EIP-7973), trustless log indexing (EIP-8304), blob-aware mempooling (EIP-8094), batch priority fees (EIP-8115), checked arithmetic (EIP-8219), account history tracking (EIP-8188), legacy deprecations like CALLCODE (EIP-2488), delayed state roots (EIP-7862), private transfers (EIP-8182), ORIGIN aliasing (EIP-7645), and SSZ execution blocks (EIP-7807).
III. In Closing
Out of the 62 proposals thoroughly evaluated by the EF Protocol cluster, exactly 2 are designated as must-ship headliners, 15 are expected to ship, and 28 have been formally declined with explicit justifications. Among the remaining proposals, 8 sit in the B tier with clearly defined inclusion requirements, 7 occupy the C tier below the viability line, and 2 remain TBD pending vital mainnet evidence. The cluster emphasizes that the success of the Hegoté upgrade will be defined just as much by the rigorous scope discipline of what is declined as by what is ultimately implemented.
Contributors and community members seeking to challenge the assigned grades or explore the underlying methodology are invited to participate in upcoming community discussions. The EF Protocol cluster is hosting a dedicated Reddit AMA on r/ethereum, where the tier list is expected to be a primary focus of discussion. Champions and advocates for proposals that did not secure A-tier placement have been encouraged to submit questions
ahead of time to engage directly with the protocol engineers shaping the future of the network.

Comments (0)