The Ethereum roadmap continues to evolve with increasing clarity as discussions around the Glamsterdam upgrade begin to solidify. While timelines are becoming more concrete, the path forward is far from simple.

Critical technical challenges, particularly around enshrined proposer-builder separation (ePBS), are forcing core developers to make foundational decisions that could reshape how Ethereum handles block production and execution coordination. At the same time, early signals for the Hegotá upgrade are emerging, with proposal pipelines beginning to take form.

• Glamsterdam Updates
• Hegota Updates

Glamsterdam Updates

Ethereum developers are converging on a clearer roadmap for Glamsterdam. Devnet 0 is targeted for mid-April 2026, ahead of interoperability (Interop) testing to ensure different clients work together. However, this timeline depends heavily on resolving the PTC fix, which is now the only hard fork (network-wide upgrade) requirement blocking progress. The PTC fix is a critical gating factor, with a firm decision deadline set for March 24, 2026. If resolved in time, Glamsterdam Devnet 0 is expected to launch in mid-April.

At the core of current discussions is ePBS. This topic continues to surface multiple technical complexities. The PTC issue introduces state-dependent changes to the committee. This raises concerns about determinism and predictability in consensus behavior.

In parallel, EIP-4788 presents challenges in handling empty payloads. Gaps may arise unless backfilling strategies are implemented. Protocols interacting with Ethereum appear to prefer backfilled data to ensure continuity. This highlights a mismatch between protocol expectations and current implementation approaches.

Execution layer requirements are also evolving under ePBS. Clients must now support reorgs to parent blocks. This increases the complexity of chain management and validation logic. Additionally, changes to communication between the consensus and execution layers are being proposed.

The Devnet 0 environment reflects both progress and instability. Clients such as Prysm, Lighthouse, and Lodestar are operational and provide a base layer for testing. However, other clients, such as Nimbus, Teku, and Grandine, are still facing issues.

Another major discussion point is the redesign of the Engine API. A proposal for SSZ-based encoding has shown significant performance gains, especially in blobs. To address coordination challenges and promote progress, some decisions have already been made.

To move forward, several coordinated action items have been assigned. Consensus layer teams are reviewing PTC fix proposals.

1. They are expected to finalize by the March 24 deadline.
2. At the same time, ecosystem stakeholders such as Lido, Rocketpool, and EigenLayer are being consulted. They will assess the impact of EIP-4788 changes.
3. Discussions around BAL Devnet 2 and Engine API improvements are also scheduled.

These will occur in upcoming core developer calls. With a compressed timeline and multiple dependencies, Glamsterdam is entering a decisive phase. Key architectural trade-offs must now be resolved quickly.

Hegota Updates

Alongside Glamsterdam, early planning for the Hegotá upgrade is beginning to take shape. The proposal pipeline for Hegotá is expected to open once the execution layer headliner decision is finalized.

This sequencing helps prevent scope creep and ensures that additional proposals align with the upgrade's overall direction. It also reflects a more structured and disciplined approach to Ethereum’s upgrade cycles compared to earlier phases of development.

One of the early candidate proposals being discussed is EIP-8148, which introduces a custom sweep threshold for 0x02 validators. This proposal aims to provide greater flexibility in how validator rewards and withdrawals are managed, enabling more granular control and potentially improving efficiency for staking participants and service providers.

While still in early stages, it signals a broader trend toward refining validator operations alongside larger protocol-level changes. As planning progresses, Hegotá is expected to build on the outcomes of Glamsterdam. It will incorporate both technical learnings and ecosystem feedback.

Glamsterdam represents a critical moment for Ethereum, during which architectural decisions on ePBS, the Engine API design, and execution-consensus coordination must be finalized under tight timelines. At the same time, the emergence of Hegotá planning shows that Ethereum’s development momentum continues beyond immediate upgrades.

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.