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 Postpones Glamsterdam Network Upgrade and Gas Limit Increase on Hoodi Testnet

Photo: Documentation / News Illustration

October 22, 2026 — Ethereum core developers have announced a temporary postponement of the highly anticipated Glamsterdam network upgrade on the Hoodi testnet, which was originally scheduled to go live alongside a significant gas-limit increase to 200 million.

The update, detailed in a protocol advisory published earlier today, supersedes all previous deployment timelines and instructions for testnet operators. The decision arrives shortly after the upgrade’s successful initial deployment on the Sepolia testnet on October 6, 2026, marking a brief pause in the broader rollout of Ethereum’s layer-one scaling roadmap. A revised schedule and updated guidance for node operators and infrastructure maintainers are expected to follow via official developer channels.

Prior to the delay, the Glamsterdam activation on Hoodi had been locked in for October 26, 2026, targeting epoch 132,352 and slot 4,235,264 at 17:42:48 UTC. Alongside the protocol changes, the network’s gas limit was slated to scale up to 200 million. While the Sepolia network successfully adopted these changes earlier this month, the mainnet activation date has intentionally remained undecided, pending thorough testing and observation across developer staging environments. Core developers have emphasized that node operators must monitor client release channels closely and ensure both their execution and consensus layer clients are fully updated once new activation parameters are confirmed.

Glamsterdam Overview

The Glamsterdam network upgrade represents a massive milestone for Ethereum, effectively combining the Amsterdam execution layer upgrade with the Gloas consensus layer upgrade. Together, these two distinct protocol branches introduce structural changes designed to dramatically improve layer-one throughput, optimize validator operations, and refine how the network prices execution and state growth.

At the heart of Glamsterdam are two headlining architectural changes: enshrined proposer-builder separation and block-level access lists. These modifications fundamentally alter how blocks are produced, validated, and processed across the Ethereum network, laying a robust foundation for future scalability without compromising the decentralization or security of node operators.

Enshrined Proposer-Builder Separation

One of the most consequential additions in the upgrade is enshrined proposer-builder separation, introduced via EIP-7732. Historically, the separation of block proposers and block builders has relied on external, trusted middleware to coordinate the exchange of execution payloads between validators and specialized block builders. EIP-7732 brings this crucial mechanism directly into Ethereum’s core consensus protocol.

Under the new enshrined framework, a block proposer includes a builder’s commitment to an execution payload within their proposal, and the builder subsequently reveals the full payload. The protocol itself handles the secure payment to the proposer, effectively removing reliance on third-party middlemen. Furthermore, the upgrade cleanly separates consensus validation from execution validation, granting validators significantly more breathing room to verify execution payloads accurately. A newly established payload timeliness committee will actively attest to whether builders reveal their payloads and ensure that corresponding blob data remains available on time. Validator operators and engineering teams maintaining builder infrastructure are strongly advised to review these new protocol duties and interfaces carefully ahead of the eventual deployment.

Block-Level Access Lists

Complementing proposer-builder separation are block-level access lists, codified under EIP-7928. This feature introduces enforced access lists that comprehensively record all accounts and storage locations accessed over the course of a single block, bundled alongside post-transaction state changes.

By having pre-declared and verified access patterns, client software can read state data from disk in parallel, validate transactions simultaneously, and compute state roots with vastly improved efficiency. Combined with ePBS, block-level access lists provide the network with an essential structural architecture to handle heavier execution loads while keeping hardware requirements and block validation times practical for home stakers and independent node operators.

Gas Pricing and State Growth

Glamsterdam also introduces comprehensive adjustments to gas accounting to ensure that transaction fees more accurately reflect actual resource consumption and long-term state bloat. Specifically, 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 adjustments target intrinsic transaction gas, calldata pricing, access lists, and overall block gas accounting metrics.

Application and smart contract developers are urged to rigorously test their contracts and gas estimation logic against these updated protocol rules. Decentralized applications and protocols that rely on fixed gas stipends, hardcoded gas limits, or narrow assumptions regarding remaining gas may experience failures or unexpected behavior and will likely require code modifications. Comprehensive tooling and impacted-contract search guidance have been provided by core developers to assist teams in auditing their codebases.

Beyond pricing adjustments, the upgrade incorporates several developer-centric improvements, including native ETH transfer logs, a dedicated slot-number opcode, a higher maximum contract size limit, a deterministic factory contract, and new stack-manipulation instructions. Consensus-layer enhancements include forward-compatible data structures, mechanisms to exclude slashed validators from the proposal queue, and increased exit and consolidation churn rates.

Security and Bug Bounties

In parallel with the testnet preparations, the Ethereum Bug Bounty Program remains fully active for all Glamsterdam specifications and improvement proposals. Client implementations become formally eligible for bounty rewards as soon as their respective software releases are integrated into official client release tables. Security researchers and developers are encouraged to review the main Ethereum bug bounty portal for detailed information regarding reward multipliers, submission requirements, and vulnerability reporting guidelines.

Client Releases and Tooling

With the Hoodi activation temporarily postponed, release schedules for compatible consensus and execution layer clients are undergoing review. Node operators are reminded that when running a validator on Ethereum, both the consensus layer beacon node and the validator client must be updated simultaneously. Only software versions that explicitly confirm support for the scheduled Glamsterdam activation should be utilized in production or testnet environments.

External tooling is also adapting to the upcoming changes. Notable components, such as Commit-Boost version 0.12.0-rc1, have begun releasing initial compatibility updates for builder infrastructure. Additional guidance for external block-building tooling will be published by maintainers as testing resumes.

Frequently Asked Questions

Ethereum network upgrades inherently require explicit, voluntary opt-in from node operators across the ecosystem. Client developers coordinate the underlying protocol changes, while validators, stakers, and non-staking node operators must independently update their software to adopt the new rules. Any node that fails to update cannot follow the upgraded network after activation, making community coordination vital for a seamless transition.

For typical Ethereum mainnet users, token holders, and holders of ETH, no direct action is required at this stage. This announcement pertains strictly to the Hoodi testnet delay, and mainnet activation details will be communicated independently once client teams reach a firm consensus. Non-staking node operators and stakers on Hoodi will need to apply the necessary client updates once the revised activation timeline is announced, ensuring that both beacon nodes and validator clients are properly configured to handle new protocol duties, ePBS interfaces, and target gas limits. Application developers should continue utilizing testnets to evaluate how repicing and state-growth modifications impact their smart contracts before any mainnet deployment takes place.

What is your reaction to this story?

Siti Muinah

Writer and contributor at Bitcoin 98.

Comments (0)