Ethereum client teams gathered during ACDC #180 to review the latest progress on the Glamsterdam upgrade while also discussing early proposals that could eventually become part of the Hegota fork. The meeting highlighted both the technical challenges facing current devnets and the longer-term scalability improvements being explored for Ethereum's consensus layer.

As Ethereum continues progressing toward the next generation of protocol upgrades, developers are simultaneously addressing implementation issues, refining networking infrastructure, improving validator APIs, and evaluating future consensus-layer optimizations. The discussions revealed how Ethereum's development process balances immediate stability concerns with long-term protocol evolution.

• Glamsterdam Updates
• Hegota Updates

Ethereum's current roadmap builds upon the foundations established during recent upgrade cycles. Readers looking for broader context can explore EtherWorld's coverage of the Glamsterdam Devnet 5 launch, as well as previous analyses of Ethereum's evolving upgrade roadmap.

Glamsterdam Updates

The primary focus of the call was the status of Glamsterdam Devnet-5, which remains unstable due to a combination of client implementation bugs and network behavior issues discovered during testing.

One major challenge involves a Prysm peering bug whose fix is currently rolling out across testing environments. At the same time, developers continue investigating a Grandine fork-choice issue that remains unresolved. Interestingly, many of these problems surfaced after testing conducted with a malicious Lodestar client that intentionally built chains on empty blocks, exposing edge cases that normal network conditions might never reveal.

Another significant topic involved PTC attestations. Developers discovered that Prysm was broadcasting invalid PTC attestations across shuffling boundaries during extended fork scenarios. A temporary mitigation has already been deployed, causing clients to skip PTC duties whenever they are not part of the committee responsible for the observed block's shuffling configuration.