The Ethereum network is on the precipice of another transformative milestone. Building upon the foundational advancements established by the recent Fusaka mainnet upgrade, the development community has officially signaled the arrival of the "Glamsterdam" network upgrade. This dual-layer update, which merges the Amsterdam execution layer improvements with the Gloas consensus layer optimizations, represents a significant leap forward in Ethereum’s long-term Layer 1 (L1) scaling roadmap.
By introducing Enshrined Proposer-Builder Separation (ePBS) and block-level access lists, Glamsterdam seeks to fundamentally reshape how blocks are produced, validated, and processed, ultimately ensuring that Ethereum remains both performant and decentralized as it scales to meet global demand.
Main Facts: The Core of the Glamsterdam Upgrade
At its heart, Glamsterdam is designed to address the increasing complexity of block validation and the limitations of current state management. The upgrade is categorized by several key technical implementations:
- Enshrined Proposer-Builder Separation (ePBS): Formally defined under EIP-7732, this change integrates the separation of block proposers and builders directly into the Ethereum protocol. Previously, this process relied on third-party, off-chain middleware. By enshrining it, the protocol reduces the trust assumptions required for the exchange of execution payloads, thereby increasing the resilience and censorship resistance of the network.
- Block-Level Access Lists (BALs): Through EIP-7928, the network will now enforce access lists that record precisely which accounts and storage slots are accessed during a block. This mechanism is critical for performance, as it enables clients to read state from the disk and validate transactions in parallel rather than in a serial, bottlenecked fashion.
- Gas Pricing Reform: A suite of EIPs, including 8037 and 8038, introduces a more granular approach to gas accounting. By separately metering the cost of state creation and updating state-access costs, the protocol ensures that gas fees more accurately reflect the underlying computational and storage resources consumed by users and developers.
The Chronology of Deployment
The activation of Glamsterdam is being handled with characteristic caution to ensure the integrity of the network. The deployment follows a rigorous testing schedule, beginning with the Sepolia testnet.
The Sepolia Milestone
The Sepolia network is scheduled to activate the Glamsterdam upgrade at epoch 353,024, slot 11,296,768. This corresponds to October 6, 2026, at 13:53:36 UTC.
| Network | Epoch | Slot | UTC Time | UNIX Timestamp |
|---|---|---|---|---|
| Sepolia | 353,024 | 11,296,768 | 2026-10-06 13:53:36 | 1791294816 |
| Hoodi | TBD | TBD | TBD | TBD |
| Mainnet | TBD | TBD | TBD | TBD |
While the Sepolia timeline is set, the broader rollout to the Hoodi testnet and eventually the Ethereum Mainnet remains subject to the results of the Sepolia activation. Client teams are currently monitoring performance and will provide a consolidated update once the testnet demonstrates stability.
Supporting Data: Infrastructure and Technical Requirements
For node operators, the transition to Glamsterdam is not merely a passive update. It requires a fundamental shift in how consensus and execution clients interact.
Client Compatibility
The success of the upgrade depends on the timely adoption of updated client versions. Node operators must ensure that both their execution layer clients (e.g., Geth, Reth, Nethermind) and consensus layer clients (e.g., Prysm, Teku, Lighthouse) are running the latest releases compatible with the Glamsterdam fork.
- Prysm: Version 7.2.0 introduces support for the Sepolia fork. Notably, users must be aware that the default gas limit shifts to 60M post-activation. For those intending to propose with a 200M gas limit, explicit configuration via version 2 proposer settings or the keymanager API is mandatory, as the
--suggested-gas-limitflag will be deprecated. - Teku: Version 26.9.1 provides the necessary support for the upgrade. Similar to Prysm, users must manually configure the gas limit using the
--validators-builder-registration-default-gas-limit=200000000flag to maintain the higher capacity.
Failure to update these configurations could lead to unintended block validation errors or, in the worst-case scenario, a node falling out of sync with the network consensus.
Official Responses and Governance Perspectives
The development process for Glamsterdam has been characterized by intense collaboration between core developers and the broader Ethereum community. Tim Beiko, a prominent voice in Ethereum’s governance, has emphasized that while the technical changes are complex, they follow the well-established "hard fork" upgrade path that the community has successfully navigated for years.
"The introduction of ePBS is a milestone for Ethereum’s decentralization," says one lead contributor involved in the EIP-7732 specification. "By bringing the builder market inside the protocol, we are effectively removing the ‘black box’ nature of current builder-proposer interactions. This is about making Ethereum’s L1 more efficient without sacrificing the core ethos of a trustless system."
Furthermore, the Ethereum Foundation has explicitly activated the Bug Bounty Program for the Glamsterdam specifications. This move serves as a final, critical layer of security, incentivizing white-hat hackers to identify potential vulnerabilities in the code before the upgrade reaches the mainnet.
Implications for the Ecosystem
The implications of Glamsterdam extend far beyond the technical architecture of the network. The shift in gas pricing, in particular, will have a tangible impact on the DApp (Decentralized Application) ecosystem.
Developers and Smart Contract Security
Application developers are urged to perform an audit of their existing smart contracts. Contracts that rely on:
- Fixed gas stipends.
- Hardcoded gas limits.
- Assumptions regarding the availability of remaining gas during execution.
…are likely to be affected. The new repricing model is intended to better align the cost of state growth with the actual strain it places on the network. Consequently, developers should utilize the "Glamsterdam Repricing Impact Guide" to simulate how their contracts will behave under the new rules. The transition period on Sepolia will serve as a sandbox for these developers to ensure their protocols remain functional and cost-efficient.
Stakers and Node Operators
For stakers, the shift toward ePBS represents a new set of duties. The protocol now distinguishes between consensus validation and execution validation, providing a cleaner separation of concerns. This allows validators to focus on their primary role—maintaining consensus—while delegating the complex, high-resource task of block building to specialized participants. This separation is expected to lower the hardware requirements for "honest" validators over time, thereby promoting a more distributed and diverse set of participants.
The Broader Vision
Ultimately, Glamsterdam is a strategic maneuver to prevent state bloat and improve throughput. By implementing block-level access lists, the network can process transactions with significantly higher parallelization. This efficiency is the "secret sauce" required to support the next wave of layer-2 rollups, which rely on the L1 for data availability and security.
Frequently Asked Questions (FAQ)
Q: As an ETH holder, do I need to move my funds?
A: No. The Glamsterdam upgrade is a protocol-level change. Your ETH will remain secure, and no action is required on your part.
Q: Why is it called "Glamsterdam"?
A: Ethereum naming conventions are consistent: Execution layer upgrades are named after the city where a major developer conference (Devcon or Devconnect) took place, while consensus layer upgrades use star names. "Glamsterdam" is a portmanteau of "Gloas" (the star) and "Amsterdam" (the site of Devconnect 2022).
Q: Where can I watch the upgrade take place?
A: The Ethereum Foundation typically hosts a livestream for major mainnet upgrades. For the Sepolia testnet activation, developers and enthusiasts are encouraged to follow the official Ethereum developer channels on GitHub and social platforms for links to real-time status dashboards.
Q: Is there any risk of a network split?
A: As with all Ethereum hard forks, there is a possibility that nodes failing to upgrade will drift onto a "stale" chain. However, because this is a coordinated upgrade supported by all major client teams and the wider community, it is expected to be a seamless transition. The primary risk is limited to operators who neglect to update their software before the specified slot/epoch.
Conclusion
The Glamsterdam upgrade serves as a testament to Ethereum’s iterative and resilient development philosophy. By tackling the difficult problems of proposer-builder separation and state-access efficiency, the network is not just maintaining its status quo—it is actively preparing for a future of higher throughput and greater decentralization.
For the community, the message is clear: monitor the Sepolia testnet, update your client software, and prepare for a more scalable, robust Ethereum. While the mainnet date remains on the horizon, the successful activation on Sepolia will be the final indicator that the network is ready for this next great leap forward.
