
Hegotá EIP Most Comprehensive Review: Where Is Ethereum's Next Hard Fork Heading?
Written by: Ethlabs
Compiled by: Chopper, Foresight News
Ethereum's development direction concerns everyone who builds applications, uses the network, holds ETH, and believes in Ethereum's future potential. Ethereum's long-term trajectory is ultimately determined by the participants who build products, operate applications, and communities on it daily, but network upgrades are the core means for protocol iteration to match user needs. Hegotá is the next network upgrade planned for Ethereum after Glamsterdam. This article will explain the directions and reasons Ethlabs believes Ethereum should prioritize in this upgrade.
Currently, the scope of the Hegotá upgrade is being初步 finalized through Ethereum's public technical process. The proposals mentioned below gather results from numerous developers, research teams, and client teams. This article clearly presents the directions Ethlabs suggests prioritizing, as well as viewpoints we have not yet finalized. We welcome all sectors of the industry to evaluate, question, and refine these claims; in the coming days and weeks, as discussions continue and information updates, we will also iterate our viewpoints.
For the Hegotá upgrade, considering all proposed EIPs, we believe the following areas are Ethereum's top priorities:
- Stronger censorship resistance: Anyone, regardless of identity or purpose, should be able to have transactions included in blocks;
- Faster Ethereum: Faster block production means faster transaction confirmation, real-time on-chain prices, and shorter finality times;
- Native Account Abstraction: Accounts support passkeys, transaction sponsorship, token payments for Gas, batched transactions, stronger privacy protection, and reserve a post-quantum key upgrade path;
- Continuous L1 Scaling: Even during peak demand periods, applications should be able to obtain stable, affordable network capacity.
Preliminary Note: How Does the EIP Promotion Process Work?
Before formally interpreting proposals, let's clarify key background: the second phase of defining the Hegotá upgrade scope has just begun. The first phase has already determined FOCIL as the core upgrade proposal for Hegotá. The deadline for non-core EIP proposals is August 6, after which the ACD meeting will comprehensively evaluate the overall Hegotá upgrade plan.
All EIPs below are currently in the PFI (Proposed for Inclusion) phase. Submitting EIPs for upgrade proposals is permissionless, but the vast majority of proposals ultimately fail to be included in formal upgrades.
As development progresses, proposals will undergo multiple rounds of review, with stages escalating and implementation certainty increasing:
PFI (Proposed for Inclusion): The proposal is submitted for this upgrade. There is no entry barrier at this stage, it does not represent client support, nor does it guarantee final launch;
CFI (Considered for Inclusion): Client teams have completed review and plan to carry out prototype development and testing;
SFI (Set for Inclusion): All parties generally agree to inclusion, provided development and testing proceed smoothly.
To understand the complete process, we recommend watching Tim Beiko's explanation video. (https://www.youtube.com/watch?v=-S4blFZl28g)
Reading Guide
This article follows Forkcast grading standards to express Ethlabs' priority judgment on various EIPs for Hegotá. To simplify decision-making, all proposals under evaluation are divided into five tiers:
- 【S Tier】Strongly recommend inclusion
- 【A Tier】Recommend inclusion if obstacles such as development difficulty, impact assessment, and ecosystem implementation are resolved
- 【B Tier】Valuable, but difficult to include in this upgrade
- 【D Tier】Under current conditions, not recommended for inclusion in Hegotá
- 【Opinion Pending】We are still evaluating this EIP
⚠️Note: The above are only Ethlabs' suggestions. We mainly evaluate based on proposal goals, technical specifications, and estimated development complexity; for projects we are deeply involved in (e.g., Frames, Quick Slots), we have more sufficient information. Subsequently, we will continue to update viewpoints based on feedback from ethPandaOps, testing teams, and various clients. The mark【CL】represents impact on Consensus Layer clients;【EL】represents impact on Execution Layer clients.
Additionally, Ethlabs participated in writing multiple EIPs (including FOCIL, Frame Transactions, Quick Slots). We strive to objectively evaluate all proposals without being influenced by our own participation, but readers may note this background when referencing viewpoints.

CL Priority List

EL Priority List
Without further ado, here are Ethlabs' complete viewpoints on the Hegotá upgrade at this stage.
Four Core Directions for Hegotá
FOCIL: Strengthen Censorship Resistance
EIP-7805 FOCIL has entered the SFI phase, formally determined as the core proposal for Hegotá. Three Ethlabs members (Francesco, Barnabé, Julian) are co-authors of this proposal, and we fully support its implementation. Since the plan is set, only a brief explanation here: only a blockchain that remains neutral to everyone can become the foundation of trust for everyone. This is the cornerstone for Ethereum scaling, growing into the true settlement layer of the global economy, and serving every participant.
Quick Slots: Faster Ethereum
Ethereum's current 12-second slot brings high latency, damaging user experience. Therefore, we strongly recommend including【CL】EIP-8198 Quick Slots【S Tier】in Hegotá, with four core reasons:
- L1 user transaction confirmation speed increases, optimizing experience;
- L1 on-chain markets obtain updated price data, improving bid-ask spreads and liquidity provider returns;
- Finality, fast confirmation rules, and slot duration are bound; faster blocks will synchronously improve Ethereum cross-chain interoperability;
- The number of block proposers per second increases, enhancing censorship resistance, including economic censorship resistance: the cost required to implement censorship by continuously emptying blocks becomes higher.
Shortening block intervals while preserving Ethereum's decentralized characteristics can increase the value of Ethereum block space, with returns flowing back to the network and ETH itself. Every reduction in latency directly creates value for users. At the same time, speed improvement is one of the improvement directions most called for by application developers.
Starting the transformation now is reasonable; slot duration adjustment cannot be achieved in one step. Consistent with scaling ideas, iterative optimization based on live testing gives application developers far more certainty than simple roadmap promises. Achieving slot times within 6 seconds is a long-term goal, with a path divided into two steps:
- One-time refactoring: Allow specifications and client code to support flexible modification of slot duration;
- Complete the first shortening in Hegotá, with subsequent hard forks continuing to reduce it, accumulating safe operation data.
Hegotá is the appropriate time to bear the one-time refactoring cost. The ePBS of the Glamsterdam upgrade has already refactored slot-related logic; consensus layer changes for this upgrade are relatively controllable. Once entering thedecoupled consensusupgrade window, consensus layer development resources will be highly紧张,and it will be difficult to have such a window period for multiple hard forks in the future.
Simply put, either maintain 12-second slots for at least the next two years, or achieve 10-second slots in the Hegotá upgrade one year later, with hope to further compress to within 10 seconds in the next round. Two speed increases are not theoretical optimizations; they can directly enhance user value and optimize the network economic model. We believe the timing is ripe.
Response to Major Controversies
We have organized four major concerns arising from preliminary communications with client development teams and the Ethereum Foundation protocol team:
- Development complexity. Millisecond-level slot timing logic has already been merged into the consensus specification via ePBS; EIP-8198 consensus layer and execution layer draft specifications are complete, base fees, Gas limits, and Blob scheduling have all been converted to ensure stable network behavior per second. Remaining work focuses on adapting various client tools based on fixed slot assumptions and boundary scenario testing. After this one-time refactoring is complete, subsequent slot shortening only requires parameter adjustment.
- zkEVM proof pressure. Two main concerns: relative proof duration, fixed proof overhead. 1) Relative proof duration: The proportion of time available for proof within the slot. Currently, block builders can start building after receiving the previous block's payload; beacon blocks confirm the current slot's payload. The payload must be proven before the next beacon proposer publishes a block. The shortest available duration for completing proof is approximately equal to one slot minus beacon block propagation delay. Propagation delay is difficult to compress, but the value itself is small and will not constitute a core bottleneck at this stage. Optimized block builders can conduct proof in parallel while assembling payload, without waiting for the winning payload to be confirmed by beacon blocks. 2) zkEVM proof overhead: Proof duration is roughly linearly related to block size, but there is fixed overhead. Faster block production means fixed overhead triggers more frequently, increasing latency under equal throughput. Under a fixed latency budget, throughput needs to be ensured without significant impact. There are two improvement paths in the industry: engineering iterations continuously reduce fixed operation time; EIP-7862 delayed state root calculation moves大量 proof work out of the critical path. Advancing both directions simultaneously means faster slots will not hinder future throughput growth.
- Post-quantum upgrade route. The decoupled consensus scheme has received sufficient support to become the stable direction for future consensus architecture. Decoupling means moving finality voting out of the block production critical path. Large-scale aggregated post-quantum signatures and recursive STARK-related logic will all depart from the critical path. Block production and fork choice rules rely only on a small group composed of an estimated 512 validators (有望 reduced to 256). Post-quantum signatures are larger, but can propagate smoothly within the planned 10-second (有望 continue to shorten) slot.
- Smart contract and infrastructure adaptation. Teams are comprehensively researching smart contract and slot duration strong coupling scenarios. We are collaborating with Sourcify to analyze all verified contracts; simultaneously evaluating the impact of slot changes on EIP-4788 (beacon block root within EVM) storing historical beacon block roots. Infrastructure level, Etherscan feedback: slot adjustment is likely to increase server load, but infrastructure already adapted to variable block times during the PoW period, so the change magnitude is controllable.
Account Abstraction: Optimize Experience, Security, and Privacy
The Ethereum ecosystem has long urgently needed native Account Abstraction (AA) to achieve experience upgrades like passkey wallets, transaction sponsorship, ERC20 payments for Gas, and batched transactions. But the path to native account abstraction implementation has been exceptionally tortuous: AA touches the entire Ethereum stack, covering clients, L2, wallets, RPC, development tools, requiring multi-party coordination. This not only makes related EIPs difficult to advance through the consensus-driven development process, but also faces ecosystem implementation difficulties after launch.
Therefore, we classify the Hegotá native AA proposal Frame Transactions as A Tier. Not because it cannot reach S Tier standards technically, but because we need to fully consider the risk of large-scale ecosystem implementation, and the coordination workload is huge. Relying on the team's accumulation in the account abstraction field, Ethlabs plans to deeply promote Frame Transactions implementation, coordinating with L2, wallets, and other participants to ensure native AA launches smoothly.
Now let's look at account abstraction related proposals for Hegotá.
【EL】EIP-8141 Frame Transactions【A Tier】
We believe Frame Transactions are the optimal solution for Ethereum native account abstraction. Compared to other native AA solutions, multiple characteristics fit Ethereum's CROPS development guidelines:
- Permissionless account innovation: Verification logic is executed by EVM code, developers can customize any verification rules; some AA solutions force whitelist verification logic, lacking flexibility;
- Native adaptation to privacy protocols: Based on the above, privacy solutions like Railgun can carry Frame transaction verification logic, users sending private transactions do not need to rely on centralized relayers, significantly improving privacy and censorship resistance;
- Designed for post-quantum security: Matched Ethereum's post-quantum roadmap from the start of development. Supports signature aggregation, even if single post-quantum signature verification costs are high, aggregation can achieve lower Gas overhead.
Frame Transactions' biggest shortcoming also stems from its flexibility: verification logic is handed over to EVM code execution, verification costs fluctuate dynamically, posing challenges for L2s pursuing high TPS.
We are optimistic that this can be solved through supporting EIP/ERC standards (e.g., EIP-7819), transactions statically declare verification logic, sequencers can bypass optimization of the verification process with native code. At the same time, we will collaborate with L2 and the Ethereum Foundation to conduct benchmark testing, locating and resolving performance bottlenecks.
[CL][EL]Frame Transactions Add-ons
There are many EIPs that can be seen as extensions of Frame transactions, and enhance their functionality on this basis.
【EL】EIP-8250 Key Nonce for Frame Transactions【A Tier】
We view this proposal as an organic component of EIP-8141 and recommend launching simultaneously. Introducing two-dimensional Nonce, accounts can send multiple transactions in parallel to the transaction mempool; privacy protocols can also store nullifiers in the two-dimensional Nonce. Two-dimensional Nonce read/write storage costs are extremely low; compared to the existing mode of writing nullifiers to ordinary storage, private transactions can save significant Gas. This is particularly important against the background of increased storage Gas costs in Glamsterdam (EIP-8037).
【EL】EIP-8272 Latest Root for Frame Transactions【B Tier】
Further optimize the experience of privacy protocols using Frame transactions. The privacy protocol verification process needs to read the latest commitment root; if stored in ordinary storage it is not only costly but also conflicts with Frame public transaction pool rules. This proposal stores root data via system contract ring buffer, automatically cleaning old data. Rated B Tier because: significantly increases Frame complexity for a single application scenario, we are uncertain if there is a more general, concise implementation solution.
【CL】EIP-8369 VOPS Profile for FOCIL Eligibility【B Tier】
Resolves interaction between Frame and VOPS (Validity Only Statelessness). The VOPS scheme allows mempool nodes to save only minimal state to verify transactions, ensuring mempool censorship resistance in a future zkEVM stateless environment. Rated B Tier because this scheme is highly bound to a statelessness route that has not yet formed community consensus.
【EL】EIP-7906 Transaction Assertions via State Diff Opcodes【B Tier】
Improve static auditability of transaction results. Users can currently assert positive results, but cannot constrain "no other state changes". To prove no additional state modifications, new opcodes are needed. Positive assertions (e.g., WETH balance increases by at least 1.5) paired with negative assertions (no other state changes), can lock all transaction impacts without simulation, hardware wallets are the core beneficiary scenario. This proposal has high complexity, inclusion in hard fork needs caution. Recommend advancing only if two conditions are met: ① Client teams fully understand all details and chain reactions; ② Test scope and potential risk assessment are complete.
【EL】EOA Migration【B Tier】
EIP-7851, EIP-8151 are suitable to be viewed together, jointly constituting an external account migration to smart account solution. Path as follows: EOA first delegates to smart account via EIP-7702; EIP-7851 adds opcode to permanently solidify delegation relationship, disabling original ECDSA keys; EIP-8151 lets ecRecover recognize keys are disabled, preventing old keys from stealing assets via Permit-like transactions. Rated B Tier: This is just one EOA migration solution, has not received extensive review and industry consensus. The biggest hidden danger lies in multi-chain compatibility: users need to repeat migration operations on every L2, including chains not yet born, user experience is poor. We look forward to a solution relying on L1 as trust root, one operation applicable to all EVM chains; only such solutions have a chance to be upgraded to A/S Tier.
【EL】Post-Quantum Signature Standards【A Tier】
Hegotá should establish a clear post-quantum signature implementation path, but needs to finalize the optimal mechanism before formal implementation. EIP-8355 adds ML-DSA precompiled contract:配合 Frame transactions, implements post-quantum account security capabilities. Alternative solutions: Pre-register support for post-quantum signatures but do not activate temporarily, or define derivation formats compatible with post-quantum keys.
【EL】EIP-7819 SETDELEGATE Instruction【A Tier】
Once native AA lands in Hegotá, reducing smart account deployment costs is crucial. But Glamsterdam's EIP-8037 will push up account creation costs. EIP-7819 allows new accounts to use lightweight delegation pointers, replacing proxy contracts, significantly reducing new state storage, lowering deployment overhead. Rated A Tier because lower account deployment costs can significantly lower the AA implementation threshold.
Performance Optimization: Continuously Promote L1 Scaling
Glamsterdam marks a shift in Ethereum R&D thinking: performance becomes the core constraint for protocol design and client development. Delayed execution, resource pricing adjustments, large-scale client optimization, increased network carrying capacity from 30 million Gas to at least 200 million Gas within two years. Performance optimization brings options; released performance margin can be used for scaling, shortening slots, lowering node hardware thresholds, or achieving multiple goals simultaneously.
Scaling demand remains urgent. Project siting not only references current Gas prices, but also looks at whether Ethereum can continue to stably expand block space supply. Continuously implementing scaling upgrades gives developers far more confidence than paper roadmaps. Mainnet still has a gap from smoothly handling traffic peaks: on Ethereum's 11th anniversary, median Gas was only about 0.1 gwei, one NFT minting event pushed Gas to the 10 gwei range, median transaction cost broke through 1 dollar. The scaling trend opened by Glamsterdam needs to continue into Hegotá.
In summary, the following EIPs continue the expansion momentum of Glamsterdam, while reinforcing the broader principles behind it: performance should always be a primary consideration in client work and protocol design.
【EL】EIP-8131 & EIP-8279【S Tier】
Data pricing combination proposal. After Glamsterdam upgrade, the network core bottleneck becomes block payload propagation. The root cause lies in inconsistent Gas accounting standards for different types of byte resources, even some are not billed. EIP-8131 unifies transaction base lower limit: extends existing transaction minimum billing rules to data confirmable before execution; EIP-8279 block access list byte lower limit: bills for access list bytes dynamically generated during execution.
Dynamic billing mechanism makes EIP-8279 more complex, but the two should be viewed bundled. The combination scheme achieves unified accounting of transaction-related bytes, limits worst-case block payload, while the vast majority of ordinary, low data occupancy transactions are unaffected. Fills resource accounting loopholes, clears obstacles for subsequent continued increase of Gas limits.
【CL】【EL】EIP-8146 【A Tier】
EIP-8146 improves the critical path itself by separating BAL and payload propagation, thereby perfecting the repricing mechanism. This not only improves propagation efficiency but also gives execution clients a head start in state prefetching and state root post-calculation. We believe this is a low-threshold optimization that cannot be missed. Implementation work is mainly based on familiar CL gossip mechanisms, so this is a low-investment, high-value EIP, especially in a branch with large EL code volume.
Other Scaling Related Proposals
【EL】CPSB Recalibration【A Tier】
Changes are simple. We recommend continuing to promote, based on planned Gas limit increases, on-chain state and execution Gas usage, choose one to include. EIP-8368 CPSB calibration adapting to new Gas limit: Follow-up supporting scheme for EIP-8037. State byte cost changes from dynamically adjusting with Gas limit to fixed value, simplifying development testing. Current CPSB is calculated based on 150 million Gas limit, after Gas limit increase, Hegotá likely needs calibration. EIP-8372 Standardize State Gas Limit: Belongs to EIP-8368 extension scheme, adjustment granularity is finer, coping with scenarios where state growth targets and regular Gas targets deviate from expectations.
【EL】EIP-7862 Delayed State Root【B Tier】
The specification itself is simple, but as far as we know, the complexity of client implementation has not been fully understood. State roots are ubiquitous in codebases. Short-term benefits are limited, core value concentrated in the long term (extending state root proof availability). Execution layer change pressure for this Hegotá is already large.
【CL】EIP-8341 Partial Execution Payload Commitment【D Tier】
Recommend not including. Benefits are limited (slightly delaying state root calculation), demand is not urgent, and EIP-7862 can achieve stronger effects, can directly replace.
Categorized Discussion of Remaining EIPs
Next, sort out remaining proposals, grouped by theme. For some proposals our viewpoints are still forming, will continue to update based on communication with client teams and authors in the future.
Hegotá is expected to be a hard fork heavy on execution layer changes, we should strictly control execution layer EIP entry thresholds. Except for FOCIL and Quick Slots, try to control consensus layer change scope: narrow upgrade scope, reserve sufficient time for client teams to cope with future large-scale architecture transitions.
【CL】Issuance Mechanism Related
We do not assign priority to EIP-8363 Progressive Issuance and Burn. Inflation issuance policy should not be unilaterally decided by core developers; priority lists equate to issuing clear implementation suggestions to core developers. The vast majority of EIPs lean towards technical decisions, the community delegates decision-making power to core development teams; but issuance mechanism belongs to monetary policy, requiring broad community consensus. Core developer opinions serve only as reference for public discussion. If ranked alongside ordinary EIPs, it equates to treating them as routine ACD technical decisions.
From a technical perspective EIP-8363 has value. As total staked ETH rises, slashing mechanism credibility declines; under high staking rates most new rewards offset inflation; scale effects continue to widen the gap between large operators and independent stakers. But changes also carry risks: staking distribution pattern has uncertainty, monetary policy solidification process will restart. Ansgar's discussion post completely lists pros and cons, consistent with our stance. Some team members previously supported adjusting issuance mechanism, currently still maintain this judgment.
We suggest, after all other scopes for Hegotá are finalized, then discuss issuance mechanism adjustments. Give the community sufficient discussion time, avoid interfering with the main line of upgrade scope definition.
【CL】Staking Function Optimization
Staking improvements have value, but prioritize optimizations for end users; pure infrastructure changes unless necessary, otherwise defer.
【CL】EIP-8015 Remove Deposit and eth1data Fields【A Tier】
Lightweight cleanup of historical technical debt. Relying on EIP-7688 forward compatible consensus data structures, irrelevant field Merkle proofs are unaffected, will not affect on-chain data readers.
【EL】【CL】EIP-8237 Consensus Layer / Execution Layer Independent Sync【B Tier】
Built on ePBS separating beacon blocks and payload, allows CL, EL to sync independently,有望 simplify client complex logic.
【CL】EIP-8205 Withdrawal Credential Pre-registration【D Tier】
Recommend not including. Although solves real pain points of delegated staking, existing deposit advance schemes can already cope, the complexity brought by adding a whole set of protocol mechanisms is difficult to match benefits at this stage.
【CL】EIP-8148 Validator Custom Liquidation Threshold【D Tier】
Recommend not including. Mechanism is complex (adds system contracts, execution requests, consensus layer logic), benefits are limited, only slightly promotes retail staking consolidation. Combined with current staking distribution pattern, difficult to significantly change全网 validator concentration trend.
【CL】EIP-8372 ePBS Execution Reward Mandatory Burn【D Tier】
Recommend not including. Likely will only spawn more off-chain channels. Years of MEV burn discussion has not formed a widely consensus solution.
【CL】EIP-7716 Anti-Correlated Proof Penalty【D Tier】
Recommend not including. Lacks sufficient evidence to support major adjustment of staking incentive mechanisms, and decoupled consensus upgrade will redesign staking incentive system.
【CL】EIP-8333 Checkpoint Alignment Epoch Boundary Blocks【D Tier】
Recommend not including. Belongs to optimization cleanup work, can be deferred to the larger scale decoupled consensus upgrade to promote together.
【CL】EIP-8359 Beacon Block Report Fields【Opinion Pending】
【CL】Post-Quantum Upgrade Preliminary Work
The following proposals reduce reliance on BLS signatures, paving the way for long-term post-quantum transition.
【CL】EIP-8365 Phase Out BLS Withdrawal Credentials【A Tier】
Phase out old-style withdrawal credentials, simplify protocol, pave the way for subsequent post-quantum transition. Changes are simple, suitable for implementation now.
【CL】EIP-8367 Phase Out BLS Validator Balance Expiry Mechanism【D Tier】
Recommend not including. The vast majority of 0x0 credential validators will complete credential migration around the time EIP-8365 launches, withdrawing funds or continuing to stake. No need to specifically add mechanisms to handle remaining stock, first implement EIP-8365 and observe actual situation.
【CL】EIP-8321 Hash Chain RANDAO【D Tier】
Recommend not including. Implementing RANDAO post-quantum security alone has limited significance, validator BLS keys still exist at risk; simultaneously each validator adds 32 bytes of data, adds new key management logic, single purpose. Complete post-quantum consensus scheme has not yet landed. We support iterative upgrades, but the first step should follow a unified roadmap, avoiding schemes being replaced by final standards.
【EL】【CL】zkEVM Adaptation Optimization
Most zkEVM preliminary optimizations have limited short-term benefits, only facilitate specific groups running full nodes, simultaneously occupy development resources, may push up EVM operation costs. Only proposals where long-term value is significantly higher than short-term costs are suitable for inclusion.
【CL】EIP-8025 Optional Execution Proof【D Tier】
Should not be included in this upgrade. The proposal itself does not mandate hard fork, bundling to Hegotá is just a priority request, we do not agree with this. Before implementing optional proof, should first clarify long-term final form, advance steadily, do not rush launch before validator/state model is finalized. Core unresolved question: Should validators retain, store partial state, or be completely stateless. Validators are an important node group, possessing hardware and network resources, changes weakening their role need higher entry standards.
【EL】EIP-7666 Identity Precompile EVM-ification【A Tier】
Changes are small, have practical value.
【EL】EIP-8200 Precompile EVM-ification【B Tier】
Use EVM bytecode to replace three types of native precompiles. Two types have low usage, migration difficulty is small; the third type is widely used for SNARK proofs. Need to complete impact assessment, confirm migration costs are controllable, or remove the third type from scope, then we will upgrade to A Tier.
【EL】EIP-7709 Read BLOCKHASH from Storage and Adjust Gas【D Tier】
Gas increase magnitude is large, disturbance is obvious, demand is not urgent. To reduce risk can carry out impact assessment, or pair with block warm-up mechanism to defer implementation.
【EL】EIP-8268 Block Access List Includes Storage Root【B Tier】
Need to assess actual impact on access list volume, transaction Gas costs (EIP-8279 will bill for access list bytes), every access account entry additionally attaches storage Merkle root.
【EL】EVM Native Functions
Hegotá will still implement some scattered EVM improvements. We believe after this upgrade, Ethereum should collaborate with the entire EVM ecosystem to formulate a long-term EVM development roadmap, Ethlabs will participate in co-construction.
【EL】EIP-5920 PAY Opcode【A Tier】
Logic is simple, is a very valuable underlying primitive for EVM. Still need to further clarify real application scenarios.
【EL】EIP-8163 Reserve EXTENSION (0xae) Opcode【A Tier】
Highly practical for L2, almost no cost for L1, serves only as a reserve identifier.
【EL】Contract Code Reuse【B Tier】
EIP-8058 Contract Bytecode Deduplication Discount, EIP-8298 SETCODEFROM Code Reuse Instruction. Rely on client storage model: contract code stored independently, accounts only point to code via code hash. Both proposals achieve same code stored only once, lowering deployment costs. Idea is attractive, but need to assess impact on forward compatibility of binary tree storage structure. No clear preference between the two proposals for now.
【EL】Memory Pricing Reform【B Tier】
We have not judged whether suitable to implement memory reform in Hegotá. Currently understanding of design space is not yet sufficient.
EIP-7686 Linear EVM Memory Limit: Changes are small, cancel quadratic growth memory expansion costs;
EIP-7923 Page-based Linear Memory Pricing: Refactors underlying rules, more complete, but complexity is higher.
【EL】EIP-8219 Arithmetic Opcodes with Overflow Check【B Tier】
Adding secure operation functions natively to EVM has value. Need benchmark testing to confirm pricing is reasonable; after completing impact assessment (benefiting transaction scale, compiler adaptation situation)有望 upgrade to A Tier.
【EL】EIP-8360 TCREATE Opcode【B Tier】
Supports creating temporary contracts within transaction lifecycle, general underlying primitive. But proposal complexity is high, can re-rate after completing development and testing difficulty assessment.
【EL】EIP-7645 ORIGIN Alias Points to SENDER【D Tier】
Recommend not including. Belongs to breaking changes, abuses ORIGIN semantics.
【EL】EIP-8182 Native Private ETH and ERC20 Transfers【D Tier】
Recommend not including. Change scale is huge, introduces ZK dependency. If implemented in future, should be as a core upgrade proposal.
【EL】EIP-2488 Deprecate CALLCODE Opcode【Opinion Pending】
【EL】EIP-4758 Disable SELFDESTRUCT【Opinion Pending】
【EL】EIP-7979 EVM Call and Return Opcodes【Opinion Pending】
【EL】EIP-8173 EVM Control Flow Basics【Opinion Pending】
【EL】EIP-8253 Zero Nonce Storage Account Nonce Auto-increment【Opinion Pending】
【EL】EIP-8030 Add P256 Algorithm Support【Opinion Pending】
【EL】EVM Pricing Mechanism
Glamsterdam increased pricing for operations with low Gas costs that constrain throughput. Hegotá related pricing proposals go in the opposite direction: reduce current operations with pricing too high, restricting application implementation costs, but contribution to network scaling is limited, belongs to icing on the cake type optimizations. We support targeted price adjustments, but proposals adding billing models must be well-designed, have determined promoters fully validating risks, before inclusion.
【EL】EIP-8358 Net Gas Billing for Account Changes【B Tier】
Benefits are questionable. Sample 900 mainnet blocks, 400,000 transactions data shows: only 2.07% transactions save Gas, saved block Gas total accounts for only 1.14%.
【EL】EIP-7973 Hot Account Write Billing【Opinion Pending】
【EL】EIP-7609 Reduce TLOAD/TSTORE Base Gas【Opinion Pending】
【EL】EIP-7971 Transient Storage Hard Cap【Opinion Pending】
【EL】EIP-3298 Cancel Gas Refund【Opinion Pending】
【EL】EIP-8374 Retain Hot Access Set After Rollback【Opinion Pending】
【EL】EIP-8115 Batch Collection of Priority Fees at Block End【Opinion Pending】
【EL】EIP-8188 Account and Storage Slot Latest Write Block Record【Opinion Pending】
【EL】【CL】Execution Data and Indexing
【EL】【CL】EIP-7668 Remove Bloom Filter【Opinion Pending】
【EL】【CL】EIP-7807 SSZ Format Execution Blocks【Opinion Pending】
【EL】EIP-8116 Simplify Cumulative Receipt Fields【Opinion Pending】
【EL】EIP-8304 Trustless Log and Transaction Indexing【Opinion Pending】
【EL】【CL】Network Layer
Ethereum P2P network still has targeted optimization space, especially transaction, Blob, proof message propagation mechanisms.
【CL】EIP-8371 RowDAS Distributed Blob Reconstruction【A Tier】
Avoid complete reconstruction, full node hosting becoming Blob scaling bottleneck. Long term, distributed reconstruction mechanism inevitably needs to be included in protocol,有望 remove validator Blob hosting requirements. Still need to further assess implementation complexity.
【CL】EIP-8142 Blob Embedded Block BiB【D Tier】
Timing is not mature, urgency insufficient, leaves large number of unresolved questions (whether to adopt KZG, new broadcast topic). Do not wish to introduce KZG mechanism into block production critical path, alternative solutions are not yet clear.
【CL】EIP-8243 Source Batch Broadcast Proof【D Tier】
Cannot clearly guarantee shortening finality time, load limit is unclear; mechanism DoS defense capability awaits verification.
【EL】EIP-8077 eth/XX Nonce-based Transaction Broadcast【Opinion Pending】
【EL】EIP-8094 eth/vhash Transaction Pool Protocol Supporting Blob【Opinion Pending】
【CL】EIP-8334 Batch Proof Broadcast【Opinion Pending】
Conclusion
Ethereum upgrades carry extremely high risk, therefore complexity is unavoidable. Thousands of nodes globally need to switch rules simultaneously in the same slot, network operation cannot be interrupted. This rigor supports Ethereum's successful upgrades history, achieving a decentralized network with zero downtime for 11 consecutive years.
Above are Ethlabs' current judgments regarding Hegotá. As development progresses, discussions deepen, once new evidence appears, we will continue to update viewpoints. Some EIPs are led by Ethlabs members, remaining proposals come from Ethereum's vast number of excellent researchers, client developers, and independent contributors. But for all solutions to land, none can depart from the coordination of client teams, wallets, applications, L2, infrastructure service providers, institutions, node operators, and end users. Ethereum belongs to the whole world, major network progress is never the result of a single organization.















