The Ethereum core developer community has announced a temporary halt to the upcoming rollout of the Glamsterdam network upgrade on the Hoodi testnet. Originally slated for activation on October 26, 2026, the deployment—which includes a significant gas-limit increase to 200 million—has been officially postponed. According to project maintainers, the previously published schedule and operator instructions have been superseded, with updated guidance and deployment timelines to be released through dedicated channels as development progresses.
The postponement arrives closely on the heels of the Glamsterdam upgrade’s successful activation on the Sepolia testnet earlier in the month, which took place on October 6. As the next major milestone in Ethereum’s Layer 1 scaling roadmap, Glamsterdam represents a foundational shift in how the network handles execution throughput, state growth, and block production. By combining the Amsterdam execution layer upgrade with the Gloas consensus layer upgrade, the package introduces complex protocol-level adjustments designed to optimize performance while ensuring that running an independent node remains feasible for operators across the global network.
Glamsterdam Overview: Scaling Execution and Refining Consensus
At the heart of the Glamsterdam upgrade are architectural changes aimed at resolving long-standing bottlenecks in Ethereum’s Layer 1 infrastructure. These changes center on enshrined proposer-builder separation and block-level access lists, two complementary mechanisms that fundamentally alter how transactions are bundled, validated, and recorded on the blockchain.
Enshrined proposer-builder separation, formally outlined in EIP-7732, brings the well-established practice of separating block proposers from block builders directly into the core consensus protocol. Under this new framework, a block proposer includes a builder’s cryptographic commitment to an execution payload, and the builder subsequently reveals that payload. The protocol natively handles the financial settlement and payment to the proposer, significantly reducing the ecosystem’s reliance on trusted third-party middleware for the exchange.
Furthermore, this separation decouples consensus validation from execution validation, granting validators crucial extra time to thoroughly check execution payloads. A dedicated payload timeliness committee will attest to whether builders reveal their payloads and ensure that corresponding blob data is made available on time. Validator operators and engineering teams maintaining builder infrastructure are advised to review these altered duties and interfaces well ahead of future deployment dates.
Complementing ePBS, EIP-7928 introduces enforced block-level access lists. These lists record the specific accounts and storage locations accessed during the lifecycle of a block, alongside post-transaction state changes. By providing this deterministic visibility, client software can read state from disk in parallel, validate transactions concurrently, and compute state roots with greater computational efficiency. Together, these enhancements form a robust foundation for scaling Ethereum’s execution capacity without compromising decentralization or inflating hardware requirements for node operators.
Gas Pricing, State Growth, and Developer Impact
As part of its comprehensive approach to network sustainability, Glamsterdam implements critical adjustments to gas accounting to better align transaction fees with actual resource consumption. EIP-8037 increases and separately meters the cost associated with creating new state, while EIP-8038 updates broader state-access costs. Additional modifications span intrinsic transaction gas requirements, calldata processing, access lists, and overall block gas accounting parameters.
These pricing modifications carry significant implications for application developers and smart contract engineers. Contracts that rely on fixed gas stipends, hardcoded gas limits, or legacy assumptions about remaining execution gas may experience unexpected failures and will require thorough code reviews. Development teams are strongly encouraged to utilize specialized repricing impact guides, search for affected contracts, and run comprehensive testing suites against the new rules on available testnets prior to mainnet deployment.
Beyond repricing, the upgrade introduces several developer-centric improvements, including native Ethereum transfer logs, a dedicated slot-number opcode, an elevated maximum contract size limit, a deterministic factory contract, and novel stack-manipulation instructions. Consensus-layer adjustments include forward-compatible data structures, measures to exclude slashed validators from the proposal queue, and increased exit and consolidation churn rates.
Security Framework and Future Activation Timelines
To safeguard the network against vulnerabilities, the Ethereum Bug Bounty Program remains fully active for 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 tables. Security researchers and developers are encouraged to review the Ethereum Bug Bounty Program documentation for detailed information regarding reward multipliers and vulnerability reporting requirements.
While the Hoodi testnet activation has been delayed, the broader deployment pipeline remains a key priority for core developers. The Sepolia testnet successfully integrated the upgrade at epoch 353,024 on October 6, 2026. However, the revised activation parameters for Hoodi—which was previously scheduled for epoch 132,352 and slot 4,235,264—will be communicated once client teams finalize a new timeline. Similarly, the official mainnet activation date remains undecided, with client developers withholding a concrete schedule until thorough testnet validation is complete.
Node operators, stakers, and infrastructure providers are advised to monitor official channels for the release of Hoodi-compatible client versions. When new software versions become available, operators must ensure that both their execution layer clients and consensus layer beacon nodes are updated prior to any future activation event. Non-staking participants, application developers, and ETH holders do not need to take immediate action regarding this Hoodi-specific announcement, though developers should continue preparing their tooling for the eventual mainnet transition.

Comments (0)