In the continuous evolution of the Ethereum network, the upcoming "Glamsterdam" upgrade represents a significant technical leap forward. Following the successful deployment of the Fusaka upgrade in late 2025, the Ethereum community is preparing for a new phase of optimization. By combining the "Amsterdam" execution layer upgrade with the "Gloas" consensus layer improvements, Glamsterdam seeks to fundamentally restructure how the network handles block production, validation, and resource pricing.
Scheduled for activation on the Sepolia testnet on October 6, 2026, at epoch 353,024 and slot 11,296,768, this upgrade is not merely a routine maintenance patch. It is a strategic advancement of Ethereum’s Layer 1 (L1) scaling roadmap, introducing enshrined Proposer-Builder Separation (ePBS) and block-level access lists to address long-standing bottlenecks in throughput and state growth.
The Core Pillars of the Glamsterdam Upgrade
The Glamsterdam upgrade centers on two transformative EIPs (Ethereum Improvement Proposals) that aim to harmonize the relationship between proposers and builders, while simultaneously optimizing how nodes process transaction data.
Enshrined Proposer-Builder Separation (ePBS)
Historically, the separation of block proposers and block builders has relied on third-party, off-protocol middleware. With the introduction of EIP-7732, Ethereum is bringing this separation directly into the consensus protocol.
Under the new system, a validator—acting as a proposer—will include a builder’s commitment to an execution payload, which the builder subsequently reveals. The protocol itself will manage the financial settlement between the two parties, effectively decentralizing a process that previously required trust in external relays. This shift not only enhances the security of the block production pipeline but also provides a more robust defense against censorship and centralized control of block content.
Furthermore, ePBS decouples consensus validation from execution validation. This allows validators more breathing room to verify complex execution payloads. A newly introduced "payload timeliness committee" will attest to whether builders have met their obligations, ensuring that blob data and execution payloads are available to the network within the necessary timeframes.
Block-Level Access Lists (BALs)
To further support the goal of increased throughput, EIP-7928 introduces mandatory block-level access lists. These lists function as a ledger of the specific accounts and storage slots accessed during the execution of a block, including all subsequent post-transaction state changes.
By providing this roadmap of state dependencies, clients can perform disk I/O and transaction validation in parallel. This is a massive optimization for node operators; it enables the network to process blocks significantly faster while maintaining the integrity of state roots. By reducing the computational overhead of block verification, BALs serve as a critical foundation for scaling the network’s execution capacity without forcing individual node operators to sacrifice hardware accessibility.
A Strategic Adjustment: Gas Pricing and State Growth
As Ethereum scales, the cost of managing the state—the permanent data stored on the blockchain—must accurately reflect the burden placed on network participants. Glamsterdam introduces a series of repricing measures, most notably EIP-8037 and EIP-8038.
EIP-8037 increases and separately meters the cost of creating new state, discouraging the proliferation of "junk" data that bloats the Ethereum state tree. Simultaneously, EIP-8038 updates the costs associated with state access. These changes, alongside adjustments to intrinsic transaction gas and calldata costs, require a paradigm shift for application developers.
Smart contract developers who rely on hardcoded gas limits or fixed stipends are being urged to audit their code immediately. The Ethereum Foundation has provided a comprehensive "Glamsterdam Repricing Impact Guide" to help developers identify vulnerable contracts that may fail or behave unpredictably post-upgrade.
Chronology and Deployment Schedule
The deployment of the Glamsterdam upgrade follows a disciplined, multi-phase rollout. While the community has finalized the timeline for the Sepolia testnet, decisions regarding the Hoodi testnet and the Ethereum Mainnet remain pending.
Activation Table for Sepolia:
- Network: Sepolia
- Epoch: 353,024
- Slot: 11,296,768
- Target Time: October 6, 2026, at 13:53:36 UTC
- UNIX Timestamp: 1,791,294,816
Node operators and validators are advised to prepare their infrastructure well in advance of the October 6 deadline. Client teams have been releasing compatible software, and it is imperative that operators update both their execution layer clients and their consensus layer (beacon) nodes. Failure to upgrade will result in nodes falling off the canonical chain once the network crosses the activation threshold.
Implications for Stakeholders
The impact of the Glamsterdam upgrade varies depending on the participant’s role within the ecosystem.
For Node Operators and Validators
For those running validation infrastructure, the requirements are more stringent than in previous upgrades. Specifically, the introduction of ePBS necessitates a review of builder-validator communication interfaces. Operators utilizing external block-building services must ensure their infrastructure is compatible with the new protocol-enshrined duties.
For instance, users of clients such as Prysm or Teku must be aware of changes to default gas limits. Version 7.2.0 of Prysm and version 26.9.1 of Teku both introduce specific configurations for proposer gas limits. Validators who wish to maintain higher gas limits (such as 200M) must explicitly set these configurations, as previous command-line flags may be deprecated or rendered ineffective by the Gloas consensus changes.
For Application Developers
Developers should view Glamsterdam as a "breaking change" upgrade. The adjustments to opcodes, state access, and gas metering mean that any contract relying on EVM internals should be re-tested in a staging environment. The addition of new stack-manipulation instructions and a higher maximum contract size offers new opportunities for complex contract deployment, but these must be balanced against the new, more accurate pricing models.
For the Average ETH Holder
For the end-user, the upgrade is largely transparent. No action is required for individual users or holders of ETH. However, the long-term benefits—increased throughput and a more sustainable state growth model—will manifest in lower fees and a more performant decentralized application (dApp) ecosystem.
Technical Nuance: Beyond the Headlines
While ePBS and BALs dominate the conversation, Glamsterdam is a comprehensive package. It includes several "quality of life" improvements that will be welcomed by the developer community:
- ETH Transfer Logs: Improving transparency for asset movements.
- Slot-number Opcode: Allowing smart contracts to be aware of their position in the consensus timeline.
- Deterministic Factory Contract: Streamlining the deployment of contract proxies.
- Consensus Churn Adjustments: Including increased exit and consolidation limits to ensure the validator set remains fluid and responsive.
Furthermore, the consensus layer is becoming more "future-proofed" with the adoption of forward-compatible data structures. By excluding slashed validators from proposing, the network continues to harden itself against malicious actors, ensuring that only honest, active participants are rewarded for their role in block production.
Security and Governance
The Ethereum Foundation has activated its Bug Bounty Program specifically for the Glamsterdam specifications. This incentivizes security researchers to audit the new code paths before they hit Mainnet. Once client releases are officially tagged as "Glamsterdam-ready," they become eligible for increased rewards, reflecting the high stakes associated with protocol-level changes.
Governance of this upgrade has followed the established "All Core Developers" (ACD) process. As articulated by long-time contributor Tim Beiko, the process is designed to ensure that every change is rigorously debated, tested on multiple testnets, and verified by diverse client teams. The name "Glamsterdam"—a portmanteau of the consensus layer upgrade "Gloas" and the location of the 2022 Devconnect, "Amsterdam"—serves as a nod to this collaborative, multi-year research effort.
Conclusion
The Glamsterdam upgrade is a testament to the maturity of the Ethereum development process. It moves the needle on the most critical challenge facing the network: scaling L1 without compromising decentralization. By enshrining the builder-proposer relationship and creating a more efficient, parallelizable state access model, Ethereum is preparing for a future where it can handle significantly higher transaction volumes.
As the industry looks toward the October 6, 2026, activation on Sepolia, the focus remains on coordination. The success of Ethereum has always been predicated on the ability of thousands of independent operators to act in concert. With the technical foundation now laid and the documentation for developers and operators published, the community is well-positioned to execute this complex transition. Whether this will lead to the "ultra-scalable" vision many proponents hope for remains to be seen, but with Glamsterdam, the roadmap is clear, and the engineering is well underway.
