Ethereum core developers continue refining the network's future upgrade roadmap through ongoing work on Glamsterdam and early discussions around Hegota, the upgrade expected to follow it. For readers tracking the broader upgrade path, EtherWorld has previously covered Glamsterdam as the next upgrade after Fusaka and the evolving Glamsterdam proposal process.

• Glamsterdam Updates
• Hegotá Updates

Glamsterdam Updates

Development efforts for Glamsterdam continue with the successful launch of Glamsterdam Devnet-5. The devnet reached genesis and entered testing with participation from multiple execution and consensus clients. Additional client teams are expected to join as testing progresses.

One major decision was the conclusion of the BAL-specific testing track. Developers confirmed that bal-devnet-7 will be the final BAL-focused devnet, with all future execution-layer testing moving into the unified Glamsterdam development framework. This should simplify coordination and reduce duplicated testing efforts.

Developers also agreed on the scope of Glamsterdam Devnet-6, expected to launch in the coming weeks. The devnet will include EIP-8038, EIP-2780, EIP-8246, and EIP-7997. These proposals focus on benchmarking, gas repricing, self-destruct cleanup, and deterministic deployment improvements.

EIP-8038 remains one of the most actively benchmarked items in the Glamsterdam pipeline. Developers reviewed recent results and noted that re-benchmarking will be needed after new optimizations. EIP-2780 was also accepted for Devnet-6, although final gas repricing numbers are still pending.

EIP-8246 focuses on removing self-destruct burn-related behavior, aligning with Ethereum's broader goal of simplifying legacy functionality. EIP-7997 introduces deterministic deployment mechanisms, improving predictability for smart contract developers and tooling providers.

Meanwhile, EIP-7610 was excluded from Devnet-6 and will require more feedback before future inclusion. This reflects Ethereum's cautious approach to upgrade scoping, similar to previous upgrade planning covered in EtherWorld's Fusaka upgrade tracker.

The meeting also included an important Engine API decision. Developers chose to adopt Marius's proposal over Barnabas's version. Teams using the alternative implementation were advised to migrate to the selected approach. Since the Engine API governs execution-consensus communication, standardization remains critical for client compatibility.

Several action items were assigned to execution-layer teams, including reviewing Engine API changes and onboarding to Devnet-5. Developers also shifted the next ACDC call to 11:00 UTC, partly to accommodate participants in other time zones.

Overall, Glamsterdam development appears to be moving steadily through testing, benchmarking, and scope refinement. The process shows Ethereum's preference for staged development and careful coordination before mainnet-facing decisions are finalized.

Hegota Updates

While Glamsterdam remains the immediate priority, developers have begun reviewing proposals that may shape Hegota, Ethereum's next major upgrade cycle.

A key discussion centered on EIP-8131 and EIP-8279, which aim to improve block efficiency and reduce worst-case resource usage. These proposals would introduce floor pricing for EIP-7702 authorizations and blob version hashes. For background on EIP-7702 and account changes, readers can revisit EtherWorld's earlier coverage of Ethereum ACDC #150 and the role of EIP-7702 in wallet upgrades.

According to estimates discussed by developers, EIP-8131 and EIP-8279 could reduce worst-case block sizes by around 40%. The proposed formula would become gas_limit/6400, giving clients a more predictable way to account for these operations.

Another major proposal was EIP-7979, positioned as a possible successor to EOF. Its key idea is moving validation logic on-chain so that clients no longer need to independently implement the same validation algorithm. Readers interested in Ethereum's evolving EOF roadmap can explore EtherWorld's coverage of the Mega EOF Endgame, which provides additional context around EVM modernization efforts.

EIP-7979 also removes separate code sections from the design, but some unresolved questions remain. Developers agreed that a dedicated breakout call should be scheduled after the draft is merged.

The call also included EIP-8222, known as Lean Staking. The proposal introduces a privacy-focused staking model using two-phase beacon deposits. However, it is currently for feedback only and is not targeting Hegota, mainly because it depends on a mature LeanVM proof system.

Privacy remains an important theme across Ethereum's roadmap. EtherWorld recently covered Vitalik Buterin's privacy-focused work through Kohaku, which connects to broader discussions around private transactions, privacy pools, and account abstraction.

Account abstraction also appeared through EIP-7851 and EIP-8151. These proposals explore permanent EOA delegation and ECRecover deactivation as part of a longer-term move away from traditional EOA key models. These proposals explore permanent EOA delegation and ECRecover deactivation as part of a longer-term move away from traditional EOA key models. Developers also discussed whether a more generic SETCODEFROM opcode could provide a cleaner design.

If you find any issues in this blog or notice any missing information, please feel free to reach out at yash@etherworld.co for clarifications or updates.

To promote your Web3 articles, events, and projects, you may reach out anytime via EtherWorld PR for submissions and collaboration.

Related Articles

1. Highlights of Ethereum's All Core Devs Meeting (ACDC) #153
2. Highlights of Ethereum's All Core Devs Meeting (ACDE) #207
3. Highlights of Ethereum's All Core Devs Meeting (ACDC) #152
4. Highlights of Ethereum's All Core Devs Meeting (ACDE) #206
5. Highlights of Ethereum's All Core Devs Meeting (ACDE) #205

To follow blockchain news, track Ethereum protocol progress, and read our latest stories, subscribe to our weekly today.