Ethereum is moving forward with its ambitious Layer 1 scaling roadmap, officially setting the stage for the major network upgrade known as "Glamsterdam." Building directly upon the foundations laid by the previous Fusaka upgrade, the upcoming network overhaul combines the Amsterdam execution layer upgrade with the Gloas consensus layer upgrade. Core developers and client teams have confirmed that the Sepolia testnet will be the first environment to experience the activation, scheduled to take place at epoch 353,024 and slot 11,296,768, which translates to October 6, 2026, at 13:53:36 UTC.
While the Sepolia testnet deployment date is firmly locked in, activation schedules for other public testnets such as Hoodi and the Ethereum mainnet remain undetermined. Client development teams will announce those timelines once further testing and network stability assessments are completed. In the meantime, node operators, stakers, infrastructure maintainers, and application developers are being urged to review the comprehensive specifications and prepare for upcoming client releases that will guarantee compatibility with the new protocol rules.
Glamsterdam Overview and Core Objectives
The Glamsterdam upgrade represents a monumental step in Ethereum’s ongoing evolution, addressing critical bottlenecks in execution throughput, state management, and block production mechanics. At its core, the upgrade introduces two headlining features: enshrined proposer-builder separation (ePBS) and block-level access lists (BALs). Together, these systemic enhancements fundamentally alter how blocks are proposed, validated, and processed, ensuring that Ethereum can scale its Layer 1 execution capacity while keeping the hardware requirements for node operators practical and sustainable.
By optimizing how data flows through the network and modernizing gas accounting rules to better reflect actual resource consumption, Glamsterdam aims to mitigate long-term state growth risks. The changes are designed to fortify the protocol’s decentralization by lowering the barriers to entry for validators while streamlining the work required by execution clients to read disk storage, validate transactions, and compute state roots.
Enshrined Proposer-Builder Separation and EIP-7732
One of the most anticipated architectural shifts included in the Glamsterdam upgrade is the implementation of enshrined proposer-builder separation, formally tracked via EIP-7732. Historically, Ethereum relied on out-of-protocol, trusted middleware mechanisms to facilitate the specialized exchange between block proposers and block builders. EIP-7732 internalizes this dynamic directly into Ethereum’s consensus protocol.
Under the new enshrined framework, a block proposer includes a builder’s commitment to a specific execution payload within a slot, and the builder subsequently reveals that payload according to protocol rules. Crucially, the protocol itself handles the payment mechanics from the builder to the proposer, drastically minimizing reliance on trusted third-party intermediaries.
Furthermore, this change decouples consensus validation from execution validation, granting validators significantly more breathing room and time to properly validate execution payloads. A dedicated payload timeliness committee will oversee the process, attesting to whether builders successfully revealed their payloads and whether the corresponding blob data was made available on schedule. Validator operators and engineering teams managing builder infrastructure must familiarize themselves with these new operational duties and protocol interfaces ahead of the testnet activation.
Block-Level Access Lists and State Optimization
Complementing ePBS, EIP-7732 introduces block-level access lists, or BALs, under EIP-7928. These enforced access lists systematically record the accounts and storage locations that are accessed throughout the duration of a block, alongside the corresponding post-transaction state changes.
By having these access lists embedded directly into the block structure, client software gains the ability to read state data from disk in parallel, validate incoming transactions concurrently, and compute state roots with unprecedented efficiency. This architectural enhancement serves as a cornerstone for scaling Ethereum’s execution environment without risking validator centralization or hardware bloat.
Gas Pricing, Repricing, and State Growth Adjustments
Glamsterdam also introduces a comprehensive overhaul of gas accounting to ensure that transaction fees more accurately reflect the true resource cost of execution and ongoing state growth. Through EIP-8037, the protocol increases and separately meters the financial and computational cost associated with creating new state. At the same time, EIP-8038 updates the base costs for general state access.
Additional modifications introduced in the upgrade affect intrinsic transaction gas, calldata handling, access lists, and broader block gas accounting metrics. Application developers and smart contract engineers are advised to proactively test their existing codebases and gas estimation models against these revised parameters. Contracts that rely on fixed gas stipends, hardcoded transaction gas limits, or legacy assumptions regarding remaining gas may fail or behave unexpectedly after activation. The Ethereum community has provided a dedicated repricing impact guide to help developers search for affected contracts and implement necessary updates.
Developer Features and Validator Improvements
Beyond its major scaling components, Glamsterdam bundles a variety of auxiliary features designed to improve the developer experience and optimize validator operations. The execution layer will benefit from the addition of native ETH transfer logs, a new slot-number opcode, an increased maximum contract size limit, a deterministic factory contract, and advanced stack-manipulation instructions.
On the consensus side, improvements include forward-compatible data structures, protocol-level rules to exclude slashed validators from proposing new blocks, and increased rates for validator exits and balance consolidations. These changes reflect a mature, highly coordinated upgrade cycle aimed at refining both user-facing utility and backend protocol stability.
Security and the Ethereum Bug Bounty Program
In alignment with previous network upgrades, the Ethereum Bug Bounty Program has been officially expanded to cover all Glamsterdam specifications and associated EIPs. Client implementations will become fully eligible for bug bounty rewards as soon as their respective software releases are formally published and integrated into the official client release schedules. Security researchers and auditors are encouraged to review the specifications and testnet releases, keeping in mind the program’s established reward multipliers and reporting protocols.
Activation Timeline and Client Release Guidance
The activation schedule for Sepolia is locked in for October 6, 2026, at epoch 353,024 and slot 11,296,768. Node operators managing non-staking nodes on Sepolia must ensure they update both their execution layer and consensus layer clients to compatible versions prior to this timestamp.
Stakers face similar operational requirements, with the critical reminder that both beacon nodes and validator clients must be fully updated. For instance, early client releases such as Prysm 7.2.0 and Teku 26.9.1 support the Sepolia fork but come with specific default configurations regarding post-activation gas limits. Validators wishing to propose blocks with higher gas limits must configure those settings explicitly according to each client’s documentation, as legacy flags may be deprecated following the activation of Gloas.
As the network approaches October 2026, Ethereum mainnet users and standard ETH holders are not required to take any immediate action, as this deployment phase is strictly confined to the Sepolia testnet. Subsequent announcements will outline the deployment pathways for Hoodi and the mainnet, marking yet another milestone in Ethereum’s relentless pursuit of decentralized scalability.

Comments (0)