The Ethereum ecosystem is taking another significant stride forward in its layer-1 scaling roadmap following the previous Fusaka upgrade. Core developers and client teams have officially announced the deployment details for the upcoming Glamsterdam network upgrade, marking a critical milestone in the protocol’s ongoing evolution. The major upgrade is scheduled to activate on the Sepolia testnet at epoch 353,024, corresponding to slot 11,296,768, which puts the exact activation time at October 6, 2026, at 13:53:36 UTC.
While the Sepolia testnet deployment date is now locked in, activation schedules for other testnets such as Hoodi, as well as the Ethereum mainnet, remain undecided and will be announced by client teams at a later date. Node operators, stakers, and infrastructure providers utilizing the Sepolia testnet are strongly advised to prepare well ahead of the October deadline, ensuring both their execution layer and consensus layer clients are updated to compatible versions before the fork occurs.
Glamsterdam Overview
The Glamsterdam network upgrade represents a comprehensive overhaul of the Ethereum protocol by combining the Amsterdam execution layer upgrade with the Gloas consensus layer upgrade. Together, these two components introduce headlining features designed to fundamentally alter how blocks are produced, validated, and processed on the network. At the core of this upgrade are enshrined proposer-builder separation and block-level access lists, two major architectural changes aimed at supporting significantly higher layer-1 throughput while maintaining the decentralization and accessibility of node operations.
Enshrined Proposer-Builder Separation
One of the most consequential changes introduced in Glamsterdam comes via EIP-7732, which brings the separation between block proposers and block builders directly into Ethereum’s consensus protocol. Previously, this separation relied on external, trusted middleware to handle the complex marketplace exchange between validators proposing blocks and specialized builders constructing them. Under the new enshrined protocol rules, a block proposer includes a builder’s commitment to an execution payload, and the builder subsequently reveals that payload within the protocol framework. Furthermore, the protocol itself natively handles the payment to the proposer, drastically reducing the reliance on third-party intermediaries and mitigating centralization risks associated with out-of-protocol relay infrastructure.
This structural shift also decouples consensus validation from execution validation, providing validators with significantly more breathing room to accurately validate execution payloads. To ensure network liveness and accountability, a newly established payload timeliness committee will attest to whether the builder successfully revealed its payload and whether the corresponding blob data was made available on time. Given the depth of these protocol modifications, validator operators and teams maintaining builder infrastructure are strongly encouraged to thoroughly review the updated duties and technical interfaces well in advance of the upgrade.
Block-Level Access Lists
Complementing the introduction of enshrined proposer-builder separation is EIP-7928, which introduces enforced block-level access lists to the network. These access lists comprehensively record the specific accounts and storage locations accessed during the execution of a block, alongside the corresponding post-transaction state changes. By embedding this information directly into the block structure, client software is empowered to read state data from disk in parallel, validate transactions simultaneously rather than sequentially, and compute state roots with unprecedented efficiency. Together, ePBS and block-level access lists lay a robust foundation for scaling Ethereum’s execution capacity while keeping the hardware requirements and validation times practical for home stakers and independent node operators.
Gas Pricing and State Growth
State bloat and resource accounting have long been central concerns for Ethereum researchers and developers. Glamsterdam addresses these challenges directly by adjusting gas accounting mechanisms to far more accurately reflect the true resource usage of network operations. Specifically, EIP-8037 increases and separately meters the financial and computational cost of creating new state, while EIP-8038 updates overall state-access costs. These modifications are accompanied by additional refinements covering intrinsic transaction gas, calldata processing, access lists, and overarching block gas accounting.
Because these changes alter the economics of smart contract execution, application developers are urged to rigorously test their contracts and gas estimation logic against the new rules. Smart contracts that rely on fixed gas stipends, hardcoded gas limits, or legacy assumptions about remaining gas may experience failures or unexpected behavior if they are not updated. The Ethereum community has provided a dedicated repricing impact guide to help developers identify affected contracts and navigate the transition safely.
Developer and Validator Improvements
Beyond its headline scaling features, Glamsterdam packs a wide array of incremental improvements for developers, stakers, and network participants. The upgrade introduces native Ethereum transfer logs, a dedicated slot-number opcode, an increased maximum contract size limit, a deterministic factory contract, and new stack-manipulation instructions designed to streamline smart contract development. On the consensus side, updates include forward-compatible data structures, protocol rules that strictly exclude slashed validators from proposing new blocks, and an increased exit and consolidation churn rate to improve validator set fluidity.
Security and Bug Bounty Programs
In alignment with standard Ethereum upgrade procedures, the Ethereum Bug Bounty Program has been officially activated for all Glamsterdam specifications and associated EIPs. Client implementations become eligible for bug bounty rewards as soon as their respective releases are officially published and integrated into the network’s release tracking tables. Security researchers and white-hat hackers looking to analyze the new specifications can consult the official Ethereum Bug Bounty Program documentation for details regarding reward multipliers, submission guidelines, and reporting requirements.
Activation Timeline and Client Releases
The agreed deployment schedule places the Sepolia testnet activation at epoch 353,024, slot 11,296,768, occurring on October 6, 2026, at 13:53:36 UTC, which translates to a UNIX timestamp of 1791294816. Hoodi and mainnet activations remain without a confirmed date and will be scheduled following the successful observation of the testnet forks.
Node operators preparing for the Sepolia activation must ensure they are running client versions that explicitly declare support for the fork. For instance, consensus layer clients such as Prysm version 7.2.0 and Teku version 26.9.1 have introduced necessary support for the Sepolia fork, though operators should note specific configuration nuances regarding default gas limits. Prysm 7.2.0 defaults to a 60M gas limit post-activation and requires explicit configuration via version 2 proposer settings or the keymanager API for validators wishing to propose with a 200M gas limit, as the older command-line flag becomes obsolete after Gloas. Similarly, Teku 26.9.1 requires explicit configuration using dedicated command-line parameters for operators aiming for higher gas limits. Execution layer client releases are rolling out concurrently, and operators utilizing external block-building infrastructure must carefully review provider-specific upgrade guidelines to ensure seamless compatibility.
Frequently Asked Questions
Network upgrades on Ethereum rely entirely on the explicit opt-in and coordination of node operators and stakers worldwide. Because the protocol enforces strict consensus rules, any node that fails to update its software will be unable to follow the upgraded chain after the activation threshold is crossed. While non-staking mainnet users and everyday ETH holders do not need to take any action regarding this specific testnet announcement, non-staking Sepolia node operators and active stakers must complete their software updates before the October deadline. Stakers, in particular, must ensure that both their beacon nodes and validator clients are fully updated and properly configured to handle new consensus duties such as ePBS.
As the Ethereum community approaches the activation date on Sepolia, developers and infrastructure teams are encouraged to continue testing applications, reviewing upcoming EIPs, and monitoring client release channels to ensure a smooth and secure upgrade process across the network’s test environments.
Comments (0)