The highly anticipated Glamsterdam network upgrade, initially slated for activation on the Hoodi testnet on October 26, 2026, has been postponed. This decision impacts not only the core upgrade but also the scheduled increase of Hoodi’s gas limit to 200 million. The Ethereum development community, responsible for coordinating these critical network enhancements, announced the delay on October 22, 2026, with a promise of further details and operator guidance to follow. While the precise reasons for the postponement have not been fully elaborated upon in the initial announcement, such delays are often attributed to the rigorous testing required for complex protocol changes, ensuring the stability and security of the Ethereum network before any widespread deployment.
This postponement signifies a temporary pause in the advancement of Ethereum’s Layer 1 scaling roadmap, a critical initiative aimed at enhancing the network’s capacity and efficiency. The Glamsterdam upgrade, a hybrid of the Amsterdam execution layer upgrade and the Gloas consensus layer upgrade, introduces several groundbreaking features designed to bolster Ethereum’s performance and decentralization. Among these are enshrined proposer-builder separation (ePBS), block-level access lists (BALs), and refined gas pricing mechanisms. These advancements collectively aim to streamline block production, improve validation processes, and ensure that gas fees more accurately reflect the true cost of on-chain operations and state growth.
The original schedule had pegged the Hoodi activation for epoch 132,352, slot 4,235,264, which corresponded to October 26, 2026, at 17:42:48 UTC. At this same epoch, the network was set to see its gas limit elevated from its current value to 200 million. This increase was intended to accommodate the enhanced transaction throughput anticipated from the new features. The mainnet activation date for Glamsterdam remains undecided, awaiting successful progression through the various testnet stages.
The news of the postponement, while a setback for those eager to see these scaling solutions implemented, underscores the Ethereum community’s commitment to a cautious and deliberate upgrade process. The focus now shifts to understanding the specific issues that led to the delay and preparing for the rescheduled activation. Node operators, a crucial component of the Ethereum network’s infrastructure, are advised to stay informed and await further instructions from the development teams.
Glamsterdam Overview: A Leap Towards Enhanced Scalability
Glamsterdam represents a significant stride in Ethereum’s ongoing evolution, aiming to address key challenges in scalability and network efficiency. The upgrade is a consolidation of two distinct but complementary upgrade paths: Amsterdam for the execution layer and Gloas for the consensus layer. By merging these efforts, the development team seeks to deliver a more robust and performant Ethereum.
The two flagship features of Glamsterdam are enshrined proposer-builder separation (ePBS) and block-level access lists (BALs). These innovations are poised to fundamentally alter how blocks are constructed and validated, paving the way for substantially higher Layer 1 throughput.
Enshrined Proposer-Builder Separation (ePBS)
At the heart of the ePBS innovation lies EIP-7732, which directly integrates the separation between block proposers and block builders into Ethereum’s consensus protocol. Historically, block proposers (validators) have been responsible for both proposing blocks and including transactions. The introduction of ePBS creates a more specialized ecosystem.
Under ePBS, a validator includes a builder’s commitment to a specific execution payload within their proposed block. The builder then reveals the actual execution payload and any associated data. Crucially, the protocol itself is designed to handle the payment from the builder to the proposer. This mechanism significantly reduces the reliance on third-party, potentially centralized, middleware solutions that have previously facilitated the exchange between proposers and builders. This trustless interaction is a cornerstone of decentralization.
Furthermore, ePBS introduces a separation between consensus validation and execution validation. This allows validators more time and flexibility to thoroughly validate the execution payloads proposed by builders. A dedicated "payload timeliness committee" will attest to whether a builder has revealed their payload and if the corresponding blob data was made available within the stipulated timeframe. This added layer of verification enhances network security and reliability.
For validator operators and teams managing builder infrastructure, understanding these new duties and interface changes is paramount. The shift necessitates careful review and adaptation of existing operational practices and tooling to align with the new protocol rules.
Block-Level Access Lists (BALs)
Complementing ePBS is EIP-7928, which introduces enforced block-level access lists. These lists meticulously record the specific accounts and storage locations that are accessed during the execution of transactions within a given block. This granular tracking, combined with post-transaction state changes, provides a comprehensive audit trail.
The implications of BALs are far-reaching for node operators. They enable clients to read state data from disk in a more parallelized fashion, significantly speeding up data retrieval. Moreover, BALs facilitate parallel transaction validation and more efficient computation of state roots. This optimization directly contributes to increased block processing capabilities and overall network throughput, making it more practical for node operators to maintain and validate the blockchain.
The synergy between ePBS and BALs is designed to create a scalable execution capacity for Ethereum while ensuring that block validation remains a feasible and practical task for the decentralized network of node operators.
Gas Pricing and State Growth: A More Accurate Reflection of Costs
Glamsterdam also brings forth significant adjustments to gas accounting, aiming to provide a more accurate representation of the computational resources consumed by network operations. EIP-8037, a key component of this initiative, increases and separately meters the cost associated with creating new state on the blockchain. This addresses the long-standing concern that state growth, which consumes valuable storage space, has not been adequately priced.
In parallel, EIP-8038 revises the costs associated with accessing existing state. These changes, along with modifications to intrinsic transaction gas, calldata costs, access lists, and the overall block gas accounting, are intended to create a more economically sound and sustainable fee market. The goal is to incentivize efficient resource utilization and discourage wasteful practices.
Application developers are strongly advised to thoroughly test their smart contracts and gas estimation tools against these new pricing mechanisms. Contracts that rely on fixed gas stipends, hardcoded gas limits, or implicit assumptions about the amount of remaining gas available may require significant modifications to function correctly post-upgrade. The "Glamsterdam repricing impact guide" provides crucial guidance for identifying affected contracts and conducting comprehensive testing.
Developer and Validator Improvements
Beyond the headline features, Glamsterdam incorporates a range of improvements designed to benefit both developers and validators. These include the introduction of ETH transfer logs for enhanced transaction tracing, a slot-number opcode for more deterministic contract execution, and an increased maximum contract size to accommodate more complex applications. A deterministic factory contract and new stack-manipulation instructions further empower developers with greater flexibility and control.
For consensus layer participants, the upgrade brings forward-compatible data structures, ensuring smoother future upgrades. It also introduces measures to prevent slashed validators from proposing blocks, enhancing network security. Additionally, changes to exit and consolidation churn aim to optimize the validator lifecycle management.
Glamsterdam Specifications: A Deeper Dive into EIPs
The Glamsterdam upgrade is formally tracked under EIP-7773. The core technical changes are encapsulated within a suite of Ethereum Improvement Proposals (EIPs), each addressing specific aspects of the upgrade. While the full list of EIPs is extensive, some of the most impactful scheduled for inclusion are:
- EIP-7732: Enshrined Proposer-Builder Separation (ePBS)
- EIP-7928: Block-Level Access Lists (BALs)
- EIP-8037: Increased and Metered State Creation Cost
- EIP-8038: Revised State Access Costs
- EIP-7773: Glamsterdam Upgrade Tracking EIP
In addition to these core EIPs, Glamsterdam also encompasses supporting networking and informational EIPs that are crucial for the smooth functioning and evolution of the network. These often include proposals related to peer-to-peer communication, data availability, and future upgradeability.
Security Considerations and Bug Bounty Program
The Ethereum Bug Bounty Program remains active and relevant for the Glamsterdam specifications and the EIPs it encompasses. As client implementations supporting Glamsterdam are released and added to the official client release tables, they become eligible for the bug bounty program. This incentivizes security researchers to identify and report vulnerabilities, thereby strengthening the network’s overall security posture. Rewards are offered for valid findings, with multipliers potentially increasing for critical bugs or those found in newly deployed features. Participants are encouraged to review the program’s guidelines for reporting requirements and reward structures.
Activation Schedule and Node Operator Responsibilities
The agreed-upon deployment schedule for Glamsterdam has historically involved a phased rollout across various testnets before mainnet activation. The original plan for the Hoodi testnet was a critical step in this process.
The proposed activation schedule was as follows:
| Network | Epoch | Slot | UTC Time | UNIX Timestamp |
|---|---|---|---|---|
| Sepolia | 353,024 | 11,296,768 | 2026-10-06 13:53:36 | 1791294816 |
| Hoodi | 132,352 | 4,235,264 | 2026-10-26 17:42:48 | 1793036568 |
| Mainnet | TBD | TBD | TBD | TBD |
The postponement of the Hoodi activation means the scheduled date of October 26, 2026, will not see the Glamsterdam upgrade go live on this testnet. The gas limit increase to 200 million, tied to this activation, is also deferred. The gas limit schedule, as outlined in EIP-8261, was intended to mirror the adjustments made on Sepolia.
For non-staking Hoodi node operators, the critical action was to update both their execution and consensus layer clients to Hoodi-compatible versions before the original activation deadline. This ensures their nodes can synchronize with the upgraded network.
For Hoodi stakers, the responsibility extended to updating both their beacon node and validator client software. This includes reviewing client-specific upgrade instructions, understanding any new duties related to ePBS, and configuring their validators to target the appropriate gas limit after activation.
Mainnet users and ETH holders were not required to take any action for this testnet upgrade. A separate, formal announcement will be made concerning the mainnet activation, outlining the timeline and necessary preparations for that critical event.
Client Releases and Tooling Updates
The successful deployment of any Ethereum network upgrade hinges on the readiness of its client software. Hoodi-compatible client releases were to be made available and listed in designated tables. Node operators were strongly advised to use only releases that explicitly confirm support for the Glamsterdam activation on Hoodi.
- Consensus Layer Hoodi Releases: These updates are crucial for validators to synchronize with the network’s consensus. Both the Beacon Node and Validator Client must be updated.
- Execution Layer Hoodi Releases: These updates ensure that nodes can correctly process and execute transactions according to the new protocol rules.
Tooling compatibility is another vital aspect. The commit-boost client, for instance, was expected to have a release candidate (0.12.0-rc1) available for testing. Beyond specific clients, builder and validator tooling compatibility guidance for Hoodi was anticipated. Operators utilizing external block-building infrastructure were also expected to consult specific upgrade instructions relevant to their setups.
Frequently Asked Questions (FAQ)
How do Ethereum network upgrades work?
Ethereum upgrades are a collaborative effort requiring explicit opt-in from node operators. Client developers coordinate protocol changes, and validators and non-staking nodes must update their software to support these new rules. Nodes that do not upgrade will be unable to participate in the network after activation, highlighting the importance of timely and coordinated updates.
As an Ethereum mainnet user or ETH holder, is there anything I need to do?
No immediate action is required for mainnet users or ETH holders in relation to this Hoodi testnet announcement. A separate announcement will detail preparations for the mainnet activation of Glamsterdam.
As a non-staking Hoodi node operator, what do I need to do?
Ensure both your execution and consensus layer clients are updated to Hoodi-compatible versions before the activation. Consult the client release tables for confirmed versions.
As a Hoodi staker, what do I need to do?
Update both your execution and consensus layer clients. Pay close attention to client-specific instructions regarding ePBS duties, tooling configurations, and gas limit settings post-activation.
As a mainnet node operator or staker, what do I need to do?
No action is required on mainnet at this time. Mainnet activation details will be communicated separately.
As an application or tooling developer, what should I do?
Review the EIPs scheduled for Glamsterdam. Test your applications on Sepolia and Hoodi post-activation. Pay special attention to changes in gas accounting, logs, opcodes, and client interfaces. The repricing impact guide is essential for identifying and updating contracts sensitive to gas assumptions.
Why "Glamsterdam"?
Ethereum’s execution layer upgrades are named after host cities of Devcon or Devconnect, while consensus layer upgrades are named after stars. "Glamsterdam" is a portmanteau of Gloas (a star name) and Amsterdam, the location of Devconnect in 2022, reflecting the combined nature of this upgrade.
The postponement of the Glamsterdam Hoodi activation, while causing a delay, underscores the Ethereum community’s dedication to a secure and stable network. The lessons learned from this pause will undoubtedly contribute to a more robust and successful eventual mainnet launch.
