Following its successful deployment on the Sepolia testnet earlier this month, the highly anticipated Glamsterdam network upgrade is officially making its next major leap toward the Ethereum mainnet. Core developers and client teams have announced that the upgrade is now formally scheduled to activate on the Hoodi testnet, marking a significant milestone in Ethereum’s ongoing layer-1 scaling roadmap. The upcoming transition is designed to fundamentally reshape how blocks are produced, validated, and priced, introducing protocol-level enhancements that promise greater throughput and efficiency for the world’s leading smart contract platform.
According to the finalized deployment schedule, the Glamsterdam network upgrade will go live on the Hoodi testnet at epoch 132,352, corresponding to slot 4,235,264. The activation is timed precisely for October 26, 2026, at 17:42:48 UTC, translating to a UNIX timestamp of 1793036568. Simultaneously, at this exact activation epoch, Hoodi’s gas limit will be raised to 200 million, mirroring the adjustments previously rolled out on Sepolia. While the testnet rollout is moving forward briskly, developers have noted that a definitive mainnet activation date has not yet been finalized and will be determined once client teams thoroughly review testnet performance.
Ahead of the scheduled activation, node operators across the ecosystem are being urged to prepare. Hoodi-compatible client versions are currently being rolled out and cataloged by development teams. Because network upgrades require explicit opt-in from the community, non-staking node operators as well as validators must update both their execution layer and consensus layer clients before the clock strikes the target slot. Operating an outdated client will result in a node becoming incompatible with the upgraded chain, severing its ability to follow the network. Staking participants running validators must ensure that both their beacon nodes and validator client software are upgraded simultaneously to avoid missing duties or facing potential penalties.
Glamsterdam Overview
The Glamsterdam upgrade represents a comprehensive overhaul of the Ethereum protocol by successfully combining the Amsterdam execution layer upgrade with the Gloas consensus layer upgrade. At its core, the combined upgrade introduces structural modifications aimed at alleviating execution bottlenecks and mitigating state growth issues. The headlining features of this release are enshrined proposer-builder separation and block-level access lists, two monumental architectural changes designed to alter how blocks are constructed and validated while preserving the decentralization and integrity of layer-1 operations.
Through these innovations, the Ethereum protocol is establishing a robust foundation for scaling execution capacity. By streamlining the way transactions are handled and verified, the network aims to make block validation more practical for node operators even as activity and data demands increase. The integration of these features has been years in the making, reflecting the collaborative efforts of researchers, client developers, and infrastructure maintainers across the broader Ethereum ecosystem.
Enshrined Proposer-Builder Separation
One of the most consequential architectural changes introduced in Glamsterdam is enshrined proposer-builder separation, codified under EIP-7732. Historically, the separation of block proposers and builders relied heavily on trusted middleware and out-of-protocol relays. EIP-7732 brings this crucial separation directly into Ethereum’s consensus protocol, fundamentally changing how blocks are proposed and finalized.
Under the new mechanism, a block proposer includes a builder’s commitment to a specific execution payload, and the builder subsequently reveals that payload according to protocol rules. Crucially, the protocol itself handles the payment mechanism from the builder to the proposer, significantly reducing reliance on trusted third-party intermediaries and external infrastructure for the exchange. Furthermore, this change cleanly separates consensus validation from execution validation. By decoupling these validation paths, validators are granted additional time to thoroughly vet execution payloads. To ensure accountability, a newly introduced payload timeliness committee actively attests to whether the builder successfully revealed its payload and whether the corresponding blob data was made available on time. Validator operators and engineering teams maintaining specialized builder infrastructure are advised to carefully review these new protocol duties and interface changes well in advance of activation.
Block-Level Access Lists
Complementing the introduction of enshrined proposer-builder separation are block-level access lists, established via EIP-7928. This protocol improvement introduces enforced access lists that comprehensively record the specific accounts and storage locations accessed over the course of an entire block, alongside post-transaction state changes.
By providing clients with explicit lists of accessed state data, the upgrade empowers execution clients to read state from disk in parallel, validate transactions concurrently, and compute state roots with vastly improved efficiency. This capability is vital for mitigating the computational bottlenecks associated with sequential state access, enabling higher transaction throughput without imposing unreasonable hardware requirements on everyday node operators.
Gas Pricing and State Growth
As Ethereum continues to mature, managing state growth and accurately pricing resource consumption remain paramount. Glamsterdam introduces significant adjustments to gas accounting to better reflect the true underlying resource usage of smart contracts and transactions. Specifically, EIP-8037 increases and separately meters the financial and computational cost of creating new state, while EIP-8038 updates state-access costs across the board. Additional modifications target intrinsic transaction gas, calldata handling, access lists, and overall block gas accounting rules.
For application developers, these changes necessitate careful auditing and rigorous testing. Contracts that rely on hardcoded gas limits, fixed gas stipends, or outdated assumptions regarding remaining gas may experience unexpected failures under the new rules. Development teams are strongly encouraged to consult the official Glamsterdam repricing impact guide, which provides search tools and testing guidance to identify potentially affected contracts and calibrate gas estimations appropriately.
Developer and Validator Improvements
Beyond its headline-grabbing scaling and pricing mechanisms, Glamsterdam delivers a rich suite of improvements designed to enhance the developer and validator experience. The upgrade incorporates a variety of execution layer enhancements, including native ETH transfer logs, a dedicated slot-number opcode, an increased maximum contract size limit, a deterministic factory contract, and novel stack-manipulation instructions.
On the consensus side, the upgrade introduces forward-compatible data structures, implements rules to explicitly exclude slashed validators from proposing new blocks, and increases the throughput for validator exits and consolidations. These improvements collectively ensure that Ethereum remains adaptable, secure, and developer-friendly as its infrastructure evolves.
Security and Bug Bounty Integration
Security remains a top priority throughout the testing and deployment lifecycle of any major Ethereum upgrade. The comprehensive Ethereum Bug Bounty Program is fully active for all Glamsterdam specifications and associated EIPs. Individual client implementations become formally eligible for bug bounty rewards as soon as their specific releases are officially incorporated into the network’s client release tables. Security researchers and developers are encouraged to review the official Ethereum bug bounty portal for detailed information regarding reward multipliers, submission guidelines, and vulnerability reporting requirements.
Client Releases and Ecosystem Readiness
With the Hoodi testnet activation date firmly locked in for late October, ecosystem participants must ensure their infrastructure is fully prepared. Node operators running non-staking nodes or validator infrastructure on Hoodi are required to update their software stack using explicitly designated client releases that confirm support for the Glamsterdam activation parameters.
Because network upgrades enforce strict protocol rules at designated boundaries, failing to update clients on time will leave nodes stranded on an incompatible chain. Stakers must pay close attention to ensure both their consensus layer beacon nodes and execution layer clients are updated in tandem. Additionally, operators utilizing external tools and specialized validator infrastructure should review compatibility notes for supporting utilities, such as commit-boost, to guarantee seamless integration with the upgraded network environment.
As the Ethereum community shifts its focus toward the Hoodi testnet deployment, the broader ecosystem continues to monitor progress closely. While mainnet timelines remain unconfirmed pending the results of testnet activations, the successful implementation of Glamsterdam on Hoodi will serve as a crucial indicator of readiness for the network’s next major evolutionary leap.
Ethereum & Smart Contracts
Ethereum & Smart Contracts
Ethereum & Smart Contracts
