The landscape of Ethereum core development is a vast, high-stakes engineering endeavor. With the rapid evolution of the network, keeping pace with the All Core Developers (ACD) meetings—where the most significant technical decisions are made—is a challenge even for seasoned industry participants. This "Checkpoint" update serves to distill the noise, providing a high-level overview of the current developmental trajectory as the Ethereum ecosystem prepares for its upcoming hard forks: Glamsterdam and Hegotá.
1. Main Facts: A Shift in Development Tempo
The primary narrative currently defining Ethereum’s development cycle is one of "slow but steady" progress. While the rapid succession of previous upgrades—such as Fusaka—had generated significant optimism regarding the velocity of protocol evolution, the current reality of the Glamsterdam upgrade is proving to be more technically demanding than initial projections suggested.
The core of the challenge lies in the implementation of enshrined Proposer-Builder Separation (ePBS). Unlike previous upgrades that often focused on optimizing existing features, ePBS requires a fundamental restructuring of how blocks are produced on the network. By shifting the responsibility of block construction from an off-chain, trust-based model to a formal, protocol-level mechanism, developers are effectively rewriting the "plumbing" of Ethereum’s consensus layer.
Alongside ePBS, the network is navigating the complexities of gas repricing. These adjustments, intended to optimize resource allocation, are not merely "tweaks" but intricate calculations that affect the entire ecosystem’s fee structure. The combination of these high-level architectural changes and more granular technical adjustments has naturally extended the timeline for the Glamsterdam deployment.
2. Chronology of Upgrades
The development pipeline is currently bifurcated into the immediate future (Glamsterdam) and the subsequent roadmap (Hegotá).
The Glamsterdam Milestone
Glamsterdam remains the current focal point for all client teams. The upgrade is organized around a mix of "Scheduled for Inclusion" (SFI) features, which are effectively locked in, and "Considered for Inclusion" (CFI) features, which remain subject to implementation feasibility and testing stability.
A critical component of this phase is the ongoing work on Block-level Access Lists (BALs). These represent a major departure from traditional state access methods and are currently undergoing rigorous stress testing on devnets. The strategy is methodical: developers are aiming for a generalized devnet deployment, contingent on the stabilization of the ePBS devnet. Once a stable environment is established, the process will move toward final client releases, exhaustive security audits, and eventual testnet deployment.
The Hegotá Horizon
Following the Glamsterdam release, the focus will shift entirely to Hegotá. During recent ACDC (All Core Developers Consensus) meetings, FOCIL (EIP-7805) was officially selected as the consensus layer headliner for this upgrade.
The path to Hegotá is currently defined by an open invitation to the broader developer community. Starting April 9th, stakeholders can submit non-headlining EIP proposals to be considered for inclusion. This democratic, albeit rigorous, process ensures that the protocol remains responsive to community needs while maintaining strict standards for security and network performance.
3. Supporting Data: Technical Challenges and Optimization
The technical burden of the current development cycle is best illustrated by the ongoing experimentation with gas limits.
- The 60M Target: While the current baseline gas limit target sits at 60M, developers are actively running simulations at significantly higher thresholds. The goal is to determine the absolute breaking point of the network and identify the optimizations required to handle such throughput safely.
- ePBS Complexity: The transition to a two-party block production model means that the consensus layer must now account for failure modes that did not exist previously. The protocol must be robust enough to handle instances where a proposer and a builder disagree or where one fails to perform their duties. This requires every layer of the Ethereum stack to be updated to recognize "partial blocks" and manage two-party coordination in real-time.
- Contract Size: Responding to community feedback, there is a strong push to prioritize EIP-7954, which would increase the maximum contract size. This is viewed by ecosystem developers as a critical improvement for scaling dApps and maintaining the competitive edge of the Ethereum Virtual Machine (EVM).
4. Official Responses and Stakeholder Engagement
The Ethereum Foundation’s Protocol Support team has been proactive in ensuring that the development process remains transparent and accessible. The recent publication of the EIP Champion’s Handbook is a direct response to the complexity of the upgrade process. It serves as a guide for those looking to introduce new features, helping them navigate the bureaucratic and technical requirements of getting a proposal from the drafting stage to final inclusion.
Furthermore, the emergence of the "strawmap"—a community-driven, non-official roadmap—has played a surprising role in guiding discussions. While not an official document, it has provided a framework for developers to align on priorities. By visualizing the "should-have" and "nice-to-have" features, the strawmap has served as a valuable tool for consensus-building during heated debates, such as the recent discourse surrounding Account Abstraction and Frame Transactions (EIP-8141).
5. Implications for the Future
The current development climate carries several significant implications for the future of the Ethereum network:
A New Standard for Account Abstraction
The debate regarding Account Abstraction, particularly the movement of EIP-8141 to "Considered for Inclusion" status, highlights a shift in strategy. Rather than forcing a specific implementation that lacks broad support, the developers have committed to a long-term goal of finding a version of Account Abstraction that satisfies the majority of stakeholders. This "placeholder commitment" signals that while the feature is a high priority, the protocol will not sacrifice technical stability for the sake of speed.
Quantum Resistance
While there is currently no standalone proposal for quantum resistance, the ongoing work on account abstraction is viewed as a prerequisite. Many developers believe that quantum-resistant features will be bundled into future, broader account abstraction packages. This reflects the reality that Ethereum’s upgrade path is becoming increasingly modular, where complex features are built upon the foundation of prior, smaller upgrades.
The Impact of "Glamsterdam" Delays
There is an implicit recognition that Glamsterdam will not be a Q2 release. While some might view this as a setback, the developer community remains remarkably composed. The sentiment among lead developers is that the complexity of the current features is far from trivial, and rushing these implementations could lead to catastrophic network failures.
The strategy has shifted from "fast forks" to "resilient forks." By taking the time to stabilize the ePBS devnets and iron out the kinks in gas repricing, the developers are ensuring that when the upgrade does finally go live, it will be battle-tested.
A Community-Driven Roadmap
Ultimately, the transition from Fusaka to Glamsterdam and then to Hegotá demonstrates the maturity of the Ethereum governance process. The ability to pivot, to debate, and to utilize tools like the strawmap to reach consensus is perhaps the most important technical feature the network has.
As we look toward the latter half of the year, the success of these upgrades will depend not just on the code, but on the continued coordination between the ACD, the client teams, and the broader community. The message is clear: Ethereum is building for the long term, and in the world of decentralized consensus, the slowest, most deliberate path is often the only one that truly leads to progress.
Appendix: Resource Overview
For those wishing to track these developments in real-time, the following resources remain the gold standard for transparency:
- Forkcast: The primary repository for tracking the progress of individual EIPs through the upgrade stages.
- ACD Call Recordings: Accessible via the Ethereum Foundation’s documentation, these transcripts and videos provide the raw, unfiltered discussions that inform the future of the protocol.
- EIP Champions Handbook: Essential reading for any developer seeking to contribute to the future of the Ethereum roadmap.
As the community looks toward the next few months, the focus remains on stabilization. With the April 9th deadline for new proposals for Hegotá fast approaching, the cycle of innovation and refinement continues, ensuring that Ethereum remains the bedrock of the decentralized web.
