The Ethereum network is poised for a significant evolution with the upcoming "Glamsterdam" upgrade, a crucial step in its long-term scaling roadmap. Following the foundational "Fusaka" upgrade, Glamsterdam introduces a suite of technical enhancements designed to bolster Ethereum’s Layer 1 (L1) scalability, improve the efficiency of block production, and refine gas pricing mechanisms. The upgrade is scheduled to activate on the Sepolia testnet on October 6, 2026, at epoch 353,024, slot 11,296,768 (13:53:36 UTC).
Glamsterdam represents a synergistic combination of the "Amsterdam" execution layer upgrade and the "Gloas" consensus layer upgrade. This integration aims to deliver substantial improvements by introducing enshrined proposer-builder separation (ePBS) and block-level access lists (BALs). These core features are engineered to fundamentally alter how blocks are produced and validated, paving the way for increased transaction throughput on Ethereum’s L1.
The activation timeline for Glamsterdam is as follows:
- Sepolia Testnet: October 6, 2026, at epoch 353,024, slot 11,296,768 (13:53:36 UTC).
- Hoodi Testnet: Activation date to be determined.
- Mainnet: Activation date to be determined.
Node operators are strongly advised to update both their execution layer (EL) and consensus layer (CL) clients to Sepolia-compatible versions prior to the scheduled activation. Client release tables will be updated as new versions are confirmed.
Enshrined Proposer-Builder Separation (ePBS)
At the heart of Glamsterdam’s scalability push is the introduction of enshrined proposer-builder separation (ePBS), formalized by EIP-7732. This groundbreaking change integrates the separation of block proposers and builders directly into Ethereum’s consensus protocol. Historically, a complex ecosystem of middleware facilitated the communication and trust between block proposers (validators) and block builders. ePBS streamlines this by allowing a proposer to include a builder’s commitment to an execution payload within the consensus layer. Subsequently, the builder reveals the actual payload and its associated blob data.
A critical advancement is that the protocol itself will now handle the payment from the builder to the proposer. This significantly reduces the reliance on third-party, potentially centralized, middleware for these crucial financial transactions, thereby enhancing the decentralization and security of block production.
Furthermore, ePBS introduces a clear separation between consensus validation and execution validation. This separation grants validators more ample time to perform thorough validation of execution payloads. A dedicated "payload timeliness committee" will attest to whether a builder has revealed its payload and if the corresponding blob data was made available within the stipulated timeframe. This architectural shift is expected to improve the robustness of the network by ensuring timely data availability and payload revelation.
Validator operators and teams managing builder infrastructure must familiarize themselves with these new duties and interfaces. Proactive review and preparation will be essential to ensure a smooth transition and leverage the benefits of ePBS.
Block-Level Access Lists (BALs)
Complementing ePBS, Block-Level Access Lists (BALs), as defined in EIP-7928, introduce a new mechanism for tracking and validating block contents. BALs enforce the recording of all accounts and storage locations accessed during the execution of transactions within a block. Crucially, they also capture the post-transaction state changes.
This detailed accounting of state access provides significant advantages for node operators. Clients will be able to read state from disk in parallel, allowing for parallel transaction validation and more efficient computation of state roots. This parallelization is a key enabler for increased L1 throughput, as it optimizes the computational bottlenecks that have historically limited transaction processing capacity. Together, ePBS and BALs are foundational elements for scaling Ethereum’s execution capacity while ensuring that block validation remains practical and accessible for node operators.
Refined Gas Pricing and State Growth Management
Glamsterdam also brings significant adjustments to Ethereum’s gas pricing mechanisms, aiming to more accurately reflect the actual resource consumption of transactions and the ongoing growth of the network’s state. These changes are critical for managing network congestion and incentivizing efficient smart contract development.
EIP-8037 introduces an increase and separate metering for the cost associated with creating new state on the blockchain. This aims to disincentivize inefficient state growth and ensure that the costs associated with expanding the Ethereum state are appropriately accounted for. Concurrently, EIP-8038 revises the costs associated with accessing existing state, further refining the economic incentives for interacting with the network.
Beyond these core EIPs, Glamsterdam incorporates several other gas-related adjustments. These include changes to intrinsic transaction gas costs, calldata pricing, the accounting of access lists, and the overall block gas accounting. These granular adjustments collectively contribute to a more robust and economically sound gas market on Ethereum.
Application developers are strongly encouraged to test their smart contracts and gas estimation tools against these new rules on the Sepolia testnet. Contracts that rely on fixed gas stipends, hardcoded gas limits, or implicit assumptions about remaining gas may require modifications to function correctly post-upgrade. A comprehensive guide detailing the impact of these repricing changes and providing guidance for affected contracts and testing procedures has been published, offering developers a roadmap for adaptation.
Developer and Validator Enhancements
Beyond the headline features, Glamsterdam integrates a range of improvements aimed at enhancing the developer experience and the operational efficiency for validators. These include the introduction of ETH transfer logs, a slot-number opcode for more precise timing information within smart contracts, and an increase in the maximum contract size. A deterministic factory contract feature is also being introduced, simplifying contract deployment and predictability.
Consensus layer changes are also part of the Glamsterdam package. These include forward-compatible data structures to facilitate future upgrades, the exclusion of slashed validators from the block proposal process to maintain network integrity, and increased flexibility in exit and consolidation churn for validators.
The complete list of Ethereum Improvement Proposals (EIPs) scheduled for inclusion in the Glamsterdam upgrade is tracked under EIP-7773. This master EIP serves as a central reference for all technical specifications.
Security and Bug Bounty Program
In line with Ethereum’s commitment to security, the Ethereum Bug Bounty Program is now active for Glamsterdam specifications and the associated EIPs. Client implementations will become eligible for bounty rewards as soon as their releases are officially added to the client release tables. This initiative encourages researchers to identify and report vulnerabilities, further strengthening the network’s security posture. Detailed information regarding reward multipliers and reporting requirements can be found on the Ethereum Bug Bounty Program website.
Background and Context: The Evolution of Ethereum Scaling
The Glamsterdam upgrade is not an isolated event but rather a continuation of Ethereum’s ongoing journey to achieve massive scalability while maintaining its core principles of decentralization and security. Following the successful Merge, which transitioned Ethereum to a Proof-of-Stake (PoS) consensus mechanism, the focus has shifted towards enhancing L1 throughput and optimizing the execution layer.
Previous upgrades, such as the "London" hard fork which introduced EIP-1559 for more predictable gas fees, and the "Shanghai" upgrade which enabled staked ETH withdrawals, have laid critical groundwork. Glamsterdam builds upon this foundation by tackling the complex challenge of increasing transaction processing capabilities directly on the mainnet. The introduction of ePBS and BALs represents a sophisticated approach to optimizing block production and validation, addressing some of the most persistent scalability bottlenecks.
The decision to combine elements of the Amsterdam (execution layer) and Gloas (consensus layer) upgrades into a single network upgrade highlights the intricate interdependencies between these two layers of the Ethereum protocol. This integrated approach aims to deliver a more cohesive and impactful set of improvements.
Expert Analysis and Implications
The introduction of ePBS is arguably the most transformative aspect of Glamsterdam. By formalizing the proposer-builder relationship and enabling protocol-level payments, Ethereum is taking a significant step towards a more robust and decentralized block production market. This could lead to increased competition among builders, potentially driving down transaction costs and improving block finality times. However, it also necessitates careful monitoring of how this new market evolves and whether it truly fosters decentralization or leads to new forms of centralization.
Block-level access lists are a more technical but equally vital upgrade. The ability to parallelize state reads and transaction validations is a direct attack on the computational limits of L1. As the Ethereum ecosystem continues to grow, this enhanced efficiency will be crucial for accommodating the increasing demand for block space. For developers, the changes in gas pricing and state access will necessitate a deeper understanding of resource utilization, potentially leading to more optimized and cost-effective smart contract designs.
The timing of the Sepolia activation in October 2026 is critical. Testnets serve as vital proving grounds, allowing developers, node operators, and users to identify and resolve any issues before the upgrade is deployed to the mainnet. This phased approach, moving from smaller testnets like Sepolia to potentially larger ones like Hoodi before the final mainnet launch, is a hallmark of the careful and iterative development process that characterizes Ethereum upgrades.
Developer and Validator Call to Action
The success of any Ethereum network upgrade hinges on the active participation of its community. Node operators, both stakers and non-stakers, must diligently update their client software. This is not merely a recommendation but a necessity to remain synchronized with the network post-activation. The provided client release tables are invaluable resources for identifying compatible software versions.
For developers, the implications of Glamsterdam are profound. The changes to gas accounting, logs, and opcodes mean that existing applications and tooling may need to be re-evaluated and updated. The repricing guide is an essential document for identifying contracts that might be negatively impacted by the new gas economics. Proactive testing on Sepolia will be key to ensuring a smooth transition for dApps and services.
Frequently Asked Questions (FAQ)
How do Ethereum network upgrades work?
Ethereum upgrades require explicit opt-in from node operators. Client developers coordinate protocol changes, and validators and non-staking nodes update their software to support them. A node that does not update cannot follow the upgraded network, making coordinated updates crucial for success.
As an Ethereum mainnet user or ETH holder, is there anything I need to do?
No. This announcement pertains to the Sepolia testnet. A separate announcement will be made regarding Glamsterdam’s mainnet activation.
As a non-staking Sepolia node operator, what do I need to do?
Update both your execution and consensus layer clients to releases that support the scheduled Sepolia activation before October 6, 2026, 13:53:36 UTC.
As a Sepolia staker, what do I need to do?
Update your execution and consensus layer clients before activation. Ensure both your beacon node and validator client are updated and review client-specific instructions regarding ePBS and builder/validator tooling.
As a Hoodi or mainnet node operator or staker, what do I need to do?
No action is required for these networks at this time. Their activation dates and compatible client releases will be announced separately.
As an application or tooling developer, what should I do?
Review the EIPs scheduled for Glamsterdam, test on Sepolia post-activation, and assess potential impacts on gas accounting, logs, opcodes, and client interfaces. Utilize the repricing impact guide to identify and update affected contracts and gas estimations.
The Glamsterdam upgrade marks another significant stride in Ethereum’s ambitious roadmap, promising enhanced scalability, improved efficiency, and a more robust decentralized future for the network. The successful activation on Sepolia will be a critical precursor to its eventual deployment on the mainnet, signaling a new era for the Ethereum ecosystem.
