The Ethereum core developer community has officially unveiled the roadmap for the upcoming Glamsterdam network upgrade, marking the next major milestone in the blockchain’s Layer 1 scaling trajectory. Following on the heels of the Fusaka upgrade, Glamsterdam introduces a sweeping suite of protocol improvements designed to fundamentally reshape how blocks are produced, validated, and accounted for on the network. The activation process is scheduled to kick off on the Sepolia testnet this autumn, bringing critical architectural shifts that developers, node operators, and stakers must prepare for in the coming months.
According to the finalized deployment schedule agreed upon by core developers, the Glamsterdam upgrade will activate on the Sepolia testnet at epoch 353,024 and slot 11,296,768, translating to October 6, 2026, at precisely 13:53:36 UTC. While Sepolia has a firm activation timestamp, deployment dates for other testnets such as Hoodi and the Ethereum mainnet remain undetermined and will be announced by client teams once further testing and readiness evaluations are complete. Consequently, everyday Ethereum mainnet users and standard ETH holders do not need to take any immediate action regarding their funds or wallets for this upcoming Sepolia-focused release.
The Glamsterdam network upgrade represents a massive collaborative undertaking, effectively combining the Amsterdam execution layer upgrade with the Gloas consensus layer upgrade. At the heart of this dual-layered overhaul are two headline features: enshrined proposer-builder separation and block-level access lists. Together, these enhancements aim to dramatically optimize Layer 1 throughput and streamline the block validation pipeline without compromising the decentralization or accessibility of network node operators.
Enshrined proposer-builder separation, formally outlined in EIP-7732, directly integrates the division between block proposers and block builders into the core Ethereum consensus protocol. Under this new mechanism, a block proposer includes a builder’s cryptographic commitment to an execution payload, after which the builder reveals the actual payload. The protocol itself oversees the payment settlement to the proposer, significantly reducing the ecosystem’s reliance on trusted external middleware for managing the complex exchange of blocks between proposers and specialized builders.
Furthermore, this architectural change decouples consensus validation from execution validation, granting validators significantly more breathing room to accurately verify execution payloads. A newly established payload timeliness committee will be tasked with attesting to whether the builder successfully revealed its payload and whether the corresponding blob data was made available on schedule. Validator operators and engineering teams maintaining builder infrastructure are strongly advised to thoroughly review these updated duties, operational requirements, and technical interfaces well ahead of activation.
Complementing proposer-builder separation is the introduction of block-level access lists via EIP-7928. These enforced lists systematically record all the specific accounts and storage locations accessed over the course of a given block, alongside the post-transaction state changes. By providing this deterministic map, client software can read state data directly from disk in parallel, execute transaction validations concurrently, and compute state roots with vastly improved efficiency. This foundation ensures that Ethereum can comfortably scale its execution capacity while keeping hardware requirements practical for independent node operators.
In tandem with structural throughput enhancements, Glamsterdam introduces comprehensive adjustments to gas pricing and accounting to better reflect the true resource costs associated with state growth. Specifically, EIP-8037 increases and separately meters the financial and computational cost of creating new state, while EIP-8038 updates broader state-access costs. Additional modifications touch upon intrinsic transaction gas, calldata handling, access lists, and overarching block gas accounting.
Application developers and smart contract engineers must thoroughly test their decentralized applications, existing contracts, and gas estimation logic against these new operational parameters. Contracts that depend heavily on fixed gas stipends, hardcoded gas limits, or legacy assumptions about remaining gas overhead may experience unexpected failures and will likely require code modifications. The core developer community has published dedicated repricing impact guides and search tools to help developers identify affected contracts prior to mainnet deployment.
Beyond scaling and gas mechanics, the Glamsterdam upgrade packs a diverse array of developer and validator improvements. These include the addition of native ETH transfer logs, a dedicated slot-number opcode, an expanded maximum contract size limit, a deterministic factory contract, and novel stack-manipulation instructions. On the consensus side, updates feature forward-compatible data structures, provisions to exclude slashed validators from the proposal queue, and an accelerated churn rate for validator exits and consolidations.
Security audits and bug hunting initiatives are already ramping up to support the upgrade cycle. The Ethereum Bug Bounty Program has officially opened its doors for the Glamsterdam specifications and associated EIPs, with client implementations becoming eligible for rewards as soon as their respective release candidates are published. Node operators have been reminded that both execution layer and consensus layer clients must be updated prior to the Sepolia activation timestamp. For stakers operating validator hardware, this requirement explicitly includes updating both the beacon node and the underlying validator client software to ensure uninterrupted participation and avoid potential penalties.
Comments (0)