BREAKING
Vercel Resolves OpenTelemetry Blind Spot in AI SDK With New Inference Duration Histogram ● YBUSDT Approaches Potential Turning Point Amid Signs of Returning Buying Interest ● SEC to Resume Processing Registration Applications ● Rarible Unveils Rebuilt Cross-Chain Marketplace Featuring High-Speed Trading and New Rewards System ● Niko Bellic Appears in GTA 6: Voice Actor Michael Hollick Returns for Late-Game Cameo ● Ant International’s Alipay+ Connects Over 50 Global E-Wallets to Brazil’s Pix to Revolutionize Cross-Border Payments ● Federal Investigation Links Ransomware Negotiation Executives to ShinyHunters Hacking Group and FBI Data Breach ● White House National Cyber Director Sean Cairncross to Step Down Amid Transitioning Political Landscape and Unexplained Tech Outages ●
Ethereum Ecosystem

Ethereum Foundation and Core Developers Schedule Glamsterdam Network Upgrade for Sepolia Testnet

Photo: Documentation / News Illustration

Ethereum core developers and client teams have officially announced the roadmap for the highly anticipated Glamsterdam network upgrade, setting its sights first on the Sepolia testnet. Building directly upon the foundations laid by the previous Fusaka upgrade, Glamsterdam represents a major milestone in Ethereum’s Layer 1 scaling trajectory. The upcoming upgrade introduces a suite of protocol changes designed to optimize block production, revamp gas economics, and streamline state management.

According to the official coordination schedule, the Glamsterdam network upgrade is scheduled to activate on the Sepolia testnet at epoch 353,024 and slot 11,296,768. This activation is slated for October 6, 2026, at precisely 13:53:36 UTC, corresponding to a UNIX timestamp of 1791294816. While Sepolia has its sights set on early October, deployment timelines for other networks, including Hoodi and the Ethereum mainnet, remain undecided and will be confirmed by developer teams at a later date.

Node operators running infrastructure on Sepolia are facing a mandatory software upgrade. Because network upgrades require explicit opt-in from participants, operators must update both their execution layer and consensus layer clients to compatible versions before the scheduled activation time. Failure to do so will leave nodes unable to follow the upgraded chain, effectively disconnecting them from the network as soon as the fork takes effect. Client teams are actively releasing compatible versions, and node operators have been advised to monitor official distribution channels closely to ensure they install releases that explicitly confirm support for the Glamsterdam Sepolia fork.

Glamsterdam Overview

The Glamsterdam network upgrade is a dual-purpose hard fork that merges the Amsterdam execution layer upgrade with the Gloas consensus layer upgrade. Together, these combined modifications overhaul the underlying mechanics of how Ethereum blocks are proposed, validated, and processed. At the core of Glamsterdam are two headlining structural implementations: enshrined proposer-builder separation and block-level access lists. These changes are engineered to dramatically improve Layer 1 transaction throughput while ensuring that validating the network remains sustainable for independent node operators.

Enshrined Proposer-Builder Separation

One of the most consequential changes introduced in Glamsterdam is enshrined proposer-builder separation, formally outlined in EIP-7732. Historically, the separation of block building and block proposing relied on off-chain, trusted middleware and relay infrastructure. EIP-7732 integrates this separation directly into Ethereum’s core consensus protocol, fundamentally altering how blocks are constructed and verified.

Under the new system, a block proposer includes a builder’s commitment to an execution payload within a slot, and the builder subsequently reveals the actual payload. The protocol natively handles the payment transaction from the builder to the proposer, significantly reducing reliance on external trusted parties. Furthermore, this mechanism completely decouples consensus validation from execution validation. By separating the two processes, validators are granted crucial additional time to thoroughly validate execution payloads. To guarantee data availability and integrity, a newly introduced payload timeliness committee actively attests to whether builders have successfully revealed their payloads and associated blob data on time. Validator operators and infrastructure maintenance teams have been strongly encouraged to review these updated duties and client interfaces well ahead of activation.

Block-Level Access Lists

Complementing proposer-builder separation, EIP-7928 introduces enforced block-level access lists to the protocol. These lists comprehensively record the specific accounts and storage locations accessed over the course of a block execution, alongside all post-transaction state changes. By providing this structured map of state access upfront, execution clients gain the ability to read state data from disk in parallel, validate transactions simultaneously rather than sequentially, and compute state roots with vastly improved efficiency. Combined with enshrined proposer-builder separation, block-level access lists provide the architectural backbone for scaling Ethereum’s execution capacity without inflating hardware requirements for validators.

Gas Pricing and State Growth

Glamsterdam also introduces critical adjustments to gas accounting to ensure that transaction fees accurately reflect the true resource consumption of network execution. EIP-8037 increases and separately meters the financial and computational cost associated with creating new state, while EIP-8038 updates general state-access costs. Additional modifications enacted during the upgrade refine intrinsic transaction gas, calldata pricing, access lists, and overarching block gas accounting.

These sweeping adjustments carry practical implications for smart contract developers and decentralized application teams. Applications relying on fixed gas stipends, hardcoded gas limits, or rigid assumptions about remaining execution gas may experience unexpected failures under the new rules. Developers are urged to audit their smart contracts and run rigorous gas estimations using dedicated impact guides and testing frameworks provided by the core development community to identify and remediate vulnerable code.

Developer and Validator Improvements

Beyond its major scaling components, the Glamsterdam upgrade packs a wide array of enhancements for developers and validators alike. The execution layer gains native ETH transfer logs, a dedicated slot-number opcode, an increased maximum contract size limit, a deterministic factory contract, and several new stack-manipulation instructions designed to optimize smart contract deployment and interaction.

On the consensus side, modifications include forward-compatible data structures, provisions to explicitly exclude slashed validators from the proposal queue, and an increased rate for validator exits and balance consolidations. These improvements collectively streamline network operations and provide developers with more expressive tooling for building advanced decentralized applications.

Glamsterdam Security

To ensure the robustness of the upgrade, the Ethereum Bug Bounty Program has officially expanded its scope to cover all Glamsterdam specifications and associated EIPs. Client implementations become eligible for bug bounty rewards as soon as their respective software releases are formally added to the official client release directories. Researchers and security auditors looking into the upgrade can consult the Ethereum Foundation’s bug bounty portal for comprehensive details regarding reward multipliers, submission guidelines, and vulnerability reporting requirements.

Client Releases and Software Compatibility

With the Sepolia activation date fast approaching, client maintainers have begun publishing compatible software versions. When operating a validator, infrastructure managers must ensure that both the consensus layer beacon node and the validator client are updated in tandem.

Specific client implementations carry unique configuration considerations that operators must address. For instance, Prysm version 7.2.0 supports the Sepolia fork but defaults to a conservative 60 million gas limit following activation. Validators aiming to propose blocks with a higher 200 million gas limit must explicitly configure this parameter using version 2 proposer settings or the keymanager API, as legacy command-line flags regarding suggested gas limits become obsolete post-Gloas. Similarly, Teku version 26.9.1 supports the Sepolia fork with a default 60 million gas limit, requiring stakers to manually adjust their configuration strings if they wish to opt into higher block gas limits. Similar considerations apply to execution layer clients and external block-building infrastructure, requiring operators to carefully review release documentation before deployment.

Frequently Asked Questions

Network upgrades on Ethereum are cooperative events that rely entirely on the voluntary participation of the global community. Upgrades require explicit opt-in from node operators, who must coordinate protocol changes by updating their software stack. Nodes that fail to adopt the new rules remain on the legacy chain and cannot follow the upgraded network after activation, making broad coordination essential for a seamless fork.

For standard Ethereum mainnet users, token holders, and participants who do not run nodes or stake, the Sepolia activation requires no direct action. A separate, dedicated announcement will be published prior to the eventual mainnet deployment of Glamsterdam. Non-staking node operators and stakers on the Sepolia testnet, however, must ensure their execution and consensus clients are fully updated prior to the October 6 deadline. Application developers are similarly advised to test their deployments against the new gas pricing models and opcode updates to maintain operational continuity.

What is your reaction to this story?

Nana Wu

Writer and contributor at Bitcoin 98.

Comments (0)