The Ethereum network’s ongoing evolution is marked by a series of complex upgrades, with the "Glamsterdam" and "Hegotā" cycles currently at the forefront of core developer discussions. While the pace of progress for Glamsterdam has proven more deliberate than initially anticipated, strategic decisions are being made for the subsequent Hegotā upgrade, signaling a continued commitment to enhancing Ethereum’s scalability, security, and functionality. This report provides a high-level overview of the current state of core development, drawing from recent All Core Developer calls and related community discussions.
Glamsterdam: Navigating the Nuances of Enshrined Proposer-Builder Separation
The Glamsterdam upgrade, slated to follow the recent Fusaka and Pectra upgrades, is experiencing a more methodical development cycle, largely due to the intricate implementation challenges associated with its flagship feature: enshrined Proposer-Builder Separation (ePBS). ePBS represents a significant architectural shift, aiming to decouple the roles of block proposers and block builders within the consensus layer. This move is intended to foster a more competitive and efficient block-building market, ultimately benefiting the network through enhanced decentralization and potentially lower transaction fees.
However, the transition to ePBS is proving to be a formidable undertaking. Unlike previous upgrades where functionalities were largely external to the core protocol, ePBS necessitates deep integration, requiring every component of the Ethereum stack to adapt. This includes the complex task of handling disagreements or failures between the newly separated proposer and builder roles. Developers are grappling with the concept of "partial blocks" and the intricacies of two-party coordination, which touches virtually every aspect of the network’s operation.
On the execution layer front, Block-level Access Lists (BALs), as proposed in EIP-7928, are another fundamental component of Glamsterdam. BALs represent a re-evaluation of how gas and state access are managed, aiming for more efficient resource utilization. The ongoing development and testing of BAL devnets are crucial for ironing out these complex issues.
Despite the complexities, a significant milestone is being pursued: the first generalized Glamsterdam devnet is targeted for release in the coming week, contingent on the stabilization of the current ePBS devnet. This devnet will serve as a crucial testing ground for integrating more of the non-headliner features. Subsequent iterations will progressively incorporate additional functionalities, allowing for rigorous testing and refinement. The process of client release, security reviews, migration to testnets, and final mainnet fork date announcement will follow once a stable devnet encompassing all intended features is achieved.
Beyond ePBS and BALs, Glamsterdam’s feature set includes several gas repricing proposals, largely being addressed as a cohesive bundle. These repricings are vital for optimizing transaction costs and improving network throughput. Furthermore, EIP-7954, which proposes an increase to the maximum contract size, has garnered considerable attention and constructive feedback from the ecosystem. Its prioritization is considered highly likely due to its potential impact on decentralized application development.
Hegotā: Charting the Course for the Next Evolutionary Leap
With Glamsterdam’s path taking shape, attention is also turning towards the subsequent upgrade, dubbed "Hegotā." The selection process for Hegotā’s major feature has concluded, with FOCIL (EIP-7805) emerging as the chosen headliner for the consensus layer. FOCIL’s inclusion signifies a continued focus on enhancing the core protocol’s efficiency and capabilities.
The execution layer has seen significant debate, particularly surrounding Account Abstraction. While there is a clear community desire to advance Account Abstraction, a lack of consensus on specific implementation choices led to EIP-8141, "Frame transactions," being moved to the "Considered for Inclusion" (CFI) status as a non-headliner feature. This decision reflects a commitment to finding an Account Abstraction solution that garners broader support among client developers, with an emphasis on community participation in shaping its final form. This approach prioritizes consensus-building over premature implementation, ensuring that future Account Abstraction features are robust and widely adopted.
The concept of quantum resistance is also gaining traction within the Ethereum community. While no standalone proposal has been formally introduced, existing Account Abstraction proposals are beginning to incorporate quantum resistance as part of a more comprehensive package. This indicates a forward-thinking approach to securing the network against future technological advancements.
The timeline for Hegotā’s non-headlining features is now open for community input. Starting April 9th, any EIP can be submitted for consideration as a non-headliner by being added to the "Proposed for Inclusion" section of the upgrade’s meta EIP (EIP-8081). The deadline for these submissions will be announced with at least two weeks’ notice, providing ample opportunity for developers to contribute. The overall timeline for the Hegotā upgrade is intrinsically linked to the progress and successful deployment of Glamsterdam, highlighting the iterative nature of Ethereum’s development roadmap.
Gas Limits and the Pursuit of Scalability
A critical area of ongoing development across both Glamsterdam and future upgrades is the increase of gas limits. Developers are actively testing higher gas limits on devnets, with a current target of 60 million for the baseline gas limit in Glamsterdam. Extensive testing is being conducted at significantly higher limits to thoroughly understand the implications and identify necessary optimizations for achieving these ambitious targets. The gas repricing efforts within Glamsterdam are foundational to enabling these safer and higher gas limits, paving the way for a more scalable Ethereum.
Empowering EIP Champions: A New Handbook for Proposal Development
In a move to streamline the proposal development and advocacy process, the Protocol Support team has launched an EIP Champion’s Handbook. This new resource, available on the Protocol Support team website, is designed to assist authors and advocates in championing feature proposals and effectively gathering stakeholder feedback. For individuals interested in contributing to future Ethereum upgrades, the handbook provides a clear roadmap through the intricate process of proposal development and adoption. This initiative underscores the commitment to fostering a more inclusive and efficient development ecosystem.
A Look Ahead: Timeline and Community Consensus
While the rapid succession of upgrades following Fusaka initially generated excitement for faster fork cycles, the current trajectory of Glamsterdam underscores the importance of thoroughness and meticulous implementation. The complexity of features like ePBS necessitates a deliberate pace. However, the clear selection of a single headliner for Hegotā, coupled with a structured process for non-headliner proposals, offers a potential for a more condensed timeline for that subsequent upgrade, contingent on the successful integration of community-driven features.
The ongoing discussions also highlight the potential for Account Abstraction to evolve from a non-headliner to a more prominent feature, should a consensus proposal emerge that aligns with community priorities. This dynamic reflects the flexible and responsive nature of Ethereum’s governance model.
The "strawmap," a community-driven document that outlines potential feature directions for future upgrades, continues to play a vital role in reigniting enthusiasm and providing a guiding framework for feature selection. This informal roadmap serves as a valuable tool for informing community consensus on upgrade priorities, complementing the official core development process.
Relevant All Core Developer Calls
The detailed discussions and decisions regarding these upgrades are meticulously documented in the minutes of the All Core Developer (ACD) calls. The period between January 21st and April 9th has seen extensive deliberation across various ACD streams, including:
- ACDT (All Core Devs Technical): Calls 76 through 67 have covered deep technical dives into the implementation details of various EIPs and architectural changes.
- ACDC (All Core Devs Consensus): Calls 176 through 173 have focused on the consensus layer aspects of the upgrades, including the intricacies of ePBS and FOCIL.
- ACDE (All Core Devs Execution): Calls 234 through 229 have addressed the execution layer implications, particularly concerning gas repricing, BALs, and Account Abstraction proposals.
These calls, along with the ongoing availability of information on platforms like Forkcast, are instrumental in maintaining transparency and fostering community engagement in the development of the Ethereum network. The commitment to iterative progress, rigorous testing, and community-driven consensus building remains central to Ethereum’s enduring evolution.
