The Ethereum development community has announced that the highly anticipated Glamsterdam network upgrade, originally slated for activation on the Hoodi testnet, has been officially postponed. This decision, communicated on October 22, 2026, halts the transition that was scheduled for October 26, which would have introduced a series of critical protocol enhancements including a significant increase to the network’s gas limit to 200 million. While the delay introduces a temporary pause in the testing schedule, it underscores the rigorous safety and coordination standards that define Ethereum’s core development lifecycle. Node operators and stakeholders are advised that all previously issued instructions regarding the October 26 deployment are now superseded, and they should refer to the latest guidance on the "Glamsterdam on Hoodi Postponed" advisory for updated timelines and operational requirements.
The Glamsterdam upgrade represents a landmark shift in Ethereum’s Layer 1 (L1) scaling strategy. By combining the Amsterdam execution layer upgrade with the Gloas consensus layer improvements, the network seeks to fundamentally reshape how blocks are produced, validated, and accounted for in terms of gas usage. The primary motivation behind this upgrade is to ensure that the protocol remains performant and sustainable as demand for block space grows, all while maintaining the decentralization that serves as the network’s foundation.
Understanding the Components of the Glamsterdam Upgrade
At its core, Glamsterdam is defined by two major technical pillars: Enshrined Proposer-Builder Separation (ePBS) and the implementation of Block-Level Access Lists (BALs).
Enshrined Proposer-Builder Separation, governed by EIP-7732, is a transformative change designed to mitigate the risks associated with the current centralized nature of block building. Under the existing framework, validators often rely on third-party relayers to outsource the complex task of transaction ordering and block construction. By "enshrining" this process into the protocol itself, Ethereum ensures that the interaction between the entity proposing the block and the entity building it is trustless and standardized. This reduces reliance on middle-layer infrastructure and introduces a formal mechanism for payment and payload commitment. Furthermore, ePBS separates consensus validation from execution validation, providing validators with a more generous window to verify execution payloads, thereby increasing network stability.
Complementing this is the introduction of Block-Level Access Lists (BALs) under EIP-7928. This feature mandates that blocks include comprehensive lists of the specific accounts and storage locations accessed during their execution, alongside post-transaction state changes. From a performance standpoint, this is a major win for node operators. With explicit access lists, client software can read state data from disk in parallel and validate transactions more efficiently. By reducing the overhead of state lookups, the network can accommodate higher throughput, addressing the long-standing challenge of L1 scaling without sacrificing the ability for individual node operators to maintain the network.
The Role of Gas Pricing and State Growth Management
A critical aspect of the Glamsterdam upgrade—and a primary reason for the focus on the 200M gas limit—is the recalibration of gas pricing to reflect the modern costs of computation and state storage. As the state size of Ethereum continues to expand, the cost of accessing or modifying that state has become a bottleneck.
Through EIP-8037 and EIP-8038, the developers have introduced a more granular metering system for state creation and access. These changes ensure that users pay fees that are more accurately aligned with the resource burden they place on the network. For application developers, this requires a transition period. Smart contracts that rely on static gas stipends or hardcoded limits may find themselves under-budgeted or incompatible with the new pricing models. Consequently, the Ethereum Foundation has released a "repricing impact guide," urging developers to perform rigorous testing on testnets before these changes reach the mainnet. The increase of the gas limit to 200 million, while aggressive, is intended to provide the headroom necessary to support the increased complexity of future decentralized applications, provided the underlying execution is optimized through the aforementioned technical changes.
Chronology and Development Roadmap
The journey toward Glamsterdam has been methodical, reflecting the industry-standard approach to Ethereum upgrades. Following the success of initial development phases, the upgrade was deployed to the Sepolia testnet on October 6, 2026, at epoch 353,024. The data collected from this deployment provided the initial insights needed for the broader rollout.
The original schedule for the Hoodi testnet was as follows:
- Announcement: October 16, 2026.
- Scheduled Activation: October 26, 2026, at 17:42:48 UTC (epoch 132,352, slot 4,235,264).
- Status: Postponed indefinitely as of October 22, 2026.
The postponement serves as a reminder that "testnets are for testing." In the context of decentralized governance, the decision to delay is not viewed as a failure, but rather as an essential mechanism for risk mitigation. By postponing the activation, the client teams ensure that they have sufficient time to address any unforeseen anomalies in client performance or synchronization issues that may have surfaced in the days leading up to the scheduled event.
Implications for Node Operators and Stakeholders
For the vast majority of users and ETH holders, the Glamsterdam upgrade and the subsequent delay will have no direct impact on their ability to transact or interact with the network. As with previous hard forks, the changes occur at the protocol layer, and as long as the majority of node operators and stakers update their clients, the network will continue to function seamlessly.
However, for node operators and stakers, the requirements are more stringent. To participate in the post-upgrade network, operators must ensure that both their execution layer clients (such as Geth, Besu, or Reth) and their consensus layer clients (such as Prysm, Lighthouse, or Teku) are running versions explicitly updated for the Glamsterdam activation. Failure to update will result in a node becoming "stuck" on a pre-fork version of the blockchain, unable to process the new transaction types or adhere to the new validation rules.
Stakers face the additional responsibility of managing their validator duties. With ePBS, there are new responsibilities regarding the timing of payload submissions and the interaction with builder infrastructure. Stakers are encouraged to monitor the client release tables closely and engage with their specific client’s documentation to understand how to adjust their infrastructure to support these new duties.
Broader Impact and Future Outlook
The "Glamsterdam" nomenclature itself—a portmanteau of "Gloas" and "Amsterdam"—highlights the collaborative nature of these upgrades. Execution layer upgrades typically draw their names from the host cities of the Ethereum developer conferences (Devcon or Devconnect), while consensus layer upgrades draw from celestial bodies. Combining these traditions reflects the increasing integration between the two layers of the network.
While the mainnet activation date remains to be decided, the delay of the Hoodi activation provides a buffer for the ecosystem to refine the implementation. The primary goal of Glamsterdam remains the long-term viability of the Ethereum mainnet as a decentralized execution layer. By tackling proposer-builder separation and state access efficiency, the network is positioning itself to handle the next wave of scaling, which will inevitably come from both layer-2 rollups and increased on-chain activity.
Industry observers note that this upgrade, once completed, will likely be one of the most technically significant since the transition to Proof-of-Stake. The shift toward a more formalized proposer-builder relationship and the optimization of state access are not merely "optimizations"—they are structural changes that address the fundamental challenges of blockchain scalability.
As the developer community continues to refine the specifications and testing parameters, the primary focus will remain on the security and liveness of the network. The Ethereum Bug Bounty Program remains active, providing a critical layer of defense by incentivizing researchers to identify potential vulnerabilities in the code before it is deployed to the production environment.
For developers, the advice remains consistent: treat the testnet as the primary sandbox for verifying how these protocol changes impact specific smart contract architectures. Whether it is updating gas estimation logic or preparing for new opcodes and log types, the time between the original schedule and the new, yet-to-be-announced date is a critical period for ensuring the transition to the new Ethereum protocol remains as smooth as possible. Further updates, including new client releases and a revised activation schedule for Hoodi, are expected to be published via official Ethereum governance channels in the coming weeks.
