The Ethereum network is on the verge of a significant technical evolution as developers finalize the preparations for the Glamsterdam network upgrade. Building directly upon the foundations laid by the previous Fusaka upgrade, which took place in late 2025, Glamsterdam represents a critical pivot point in Ethereum’s long-term Layer 1 (L1) scaling roadmap. By introducing structural changes to how blocks are produced, validated, and priced, this upgrade seeks to balance the dual requirements of increased throughput and sustainable state growth. The activation for the Sepolia testnet is officially scheduled for epoch 353,024, at slot 11,296,768, which corresponds to October 6, 2026, at 13:53:36 UTC.
This milestone is the result of months of collaborative development between client teams, researchers, and infrastructure providers. As with previous major network upgrades, the path to Glamsterdam has been defined by a rigorous process of specification, testing, and consensus-building. While mainnet and Hoodi testnet activation dates remain subject to further coordination and successful performance metrics from the Sepolia deployment, the upcoming testnet activation marks the first major real-world stress test for the new protocols being introduced.
The Technical Pillars of Glamsterdam: ePBS and BALs
The primary objective of the Glamsterdam upgrade is to move the Ethereum protocol toward a more efficient and decentralized architecture. At the heart of this effort are two headline improvements: Enshrined Proposer-Builder Separation (ePBS) and Block-Level Access Lists (BALs).
Enshrined Proposer-Builder Separation, codified under EIP-7732, represents a fundamental shift in the relationship between block proposers (validators) and block builders. In the current Ethereum architecture, this separation is handled by off-protocol, trusted middleware. By enshrining this process within the consensus protocol itself, Ethereum aims to reduce reliance on third-party intermediaries, thereby enhancing the network’s censorship resistance and overall security. Under the new framework, a proposer will include a builder’s commitment to an execution payload, with the builder revealing the actual payload in a subsequent step. This mechanism not only secures the payment flow to the proposer but also decouples consensus validation from execution validation, granting validators more time to perform necessary checks. Furthermore, the introduction of a "payload timeliness committee" provides an additional layer of verification, ensuring that both the execution payload and corresponding blob data are available to the network in a timely manner.
Complementing ePBS are Block-Level Access Lists, as outlined in EIP-7928. Access lists serve as a roadmap of the accounts and storage locations that will be touched during a block’s execution, along with the subsequent state changes. By mandating these lists at the block level, the protocol enables Ethereum clients to read state from disk in parallel and validate transactions more efficiently. This architectural shift addresses one of the most persistent bottlenecks in Ethereum’s scaling journey: the sequential nature of state access. By allowing for parallelized execution and state root computation, the network can accommodate higher throughput without necessitating a proportional increase in the hardware requirements for node operators.
Resource Accounting: Gas Pricing and State Growth
As Ethereum’s state size continues to grow, the cost of maintaining and accessing that state has become a primary concern for the core development community. Glamsterdam introduces a series of adjustments to gas accounting intended to more accurately reflect the resource footprint of transactions.
EIP-8037 and EIP-8038 are the key components of this repricing strategy. The former increases and introduces separate metering for the cost of state creation, ensuring that users who expand the network’s state footprint pay a fee commensurate with the long-term storage burden they impose. The latter updates the costs associated with general state access. Together, these changes—coupled with updates to intrinsic transaction gas, calldata, and block gas accounting—aim to optimize the distribution of costs within the Ethereum ecosystem.
For developers, these changes necessitate a proactive approach to smart contract auditing and gas estimation. Contracts that rely on legacy assumptions, such as hardcoded gas limits or fixed stipends, may face execution failures post-upgrade. To mitigate these risks, developers are encouraged to utilize the "Glamsterdam Repricing Impact Guide," a resource provided by the core dev team to help identify and remediate potentially affected contracts before the upgrade goes live on mainnet.
A Chronology of Coordination and Governance
The path to the Glamsterdam upgrade began shortly after the successful deployment of the Fusaka upgrade in November 2025. Following the stabilization of the network, the Ethereum All Core Developers (ACD) meetings shifted focus toward the next iteration of the roadmap. The naming convention of "Glamsterdam"—a portmanteau of the "Gloas" consensus layer upgrade and the "Amsterdam" execution layer upgrade—reflects the collaborative nature of the development process. Consistent with Ethereum’s naming tradition, execution layer upgrades are named after cities that have hosted major developer events like Devcon or Devconnect, while consensus layer upgrades adopt the names of stars.
Throughout 2026, the specifications for the upgrade underwent extensive review on GitHub, followed by rigorous testing on internal development networks (devnets). The decision to target Sepolia for the initial public testnet activation on October 6, 2026, was reached following consensus among client teams during the September 2026 planning sessions. This strategic delay allows for a thorough vetting of client implementations—such as Prysm and Teku—ensuring that node operators have ample time to update their software.
Implications for Node Operators and Validators
For the broader Ethereum community, the Glamsterdam upgrade reinforces the importance of active participation in network maintenance. Unlike centralized systems, Ethereum’s upgrade path relies on the explicit opt-in of node operators. A node that fails to update its software before the epoch 353,024 threshold will be unable to process blocks under the new consensus rules, effectively becoming incompatible with the rest of the network.
Validators, in particular, face more complex responsibilities under the new ePBS regime. With the introduction of new duties, operators of both the consensus layer beacon node and the validator client must ensure their infrastructure is fully compliant with the latest specifications. For instance, specific configuration changes regarding gas limits—such as the 200M gas limit options provided in the latest Prysm and Teku releases—require manual intervention from stakers. Failure to properly configure these settings could result in missed proposals or reduced efficiency, underscoring the need for a deep understanding of the new client-side interfaces.
Future Outlook and Strategic Context
The significance of Glamsterdam extends beyond its immediate technical changes. It represents a pivotal transition in Ethereum’s strategy to become a high-throughput, modular blockchain. By offloading the complexity of execution to specialized builders while maintaining a decentralized consensus layer, Ethereum is positioning itself to better serve the needs of Layer 2 (L2) rollups, which rely heavily on the L1 for data availability and security.
The move toward more efficient state access and optimized gas pricing is a necessary precursor to future scaling efforts, such as Verkle trees and other state-minimization techniques currently in the research phase. As Ethereum continues to mature, the focus is increasingly shifting toward "sustainability of operation"—ensuring that the network can remain performant even as the volume of transactions and the size of the global state continue to climb.
While the community awaits the activation on Sepolia, the atmosphere among core developers remains one of cautious optimism. The rigorous bug bounty program associated with the Glamsterdam specifications, hosted by the Ethereum Foundation, serves as an additional safeguard against unforeseen vulnerabilities. By incentivizing the discovery of flaws before they reach the mainnet, the foundation aims to maintain the high standard of reliability that has characterized Ethereum’s post-Merge history.
Ultimately, the Glamsterdam upgrade is a testament to the resilience of the Ethereum development model. Despite the inherent difficulties of coordinating a decentralized, global network of thousands of independent node operators, the protocol continues to iterate at a steady pace. As the October 6, 2026, activation approaches, the eyes of the crypto-economic world will be on Sepolia, watching to see how these ambitious changes manifest in a live environment. For the users, investors, and developers who form the backbone of the Ethereum ecosystem, this upgrade is not merely a software update, but a critical step toward realizing the vision of a globally scalable, decentralized computing platform.
