Skip to content
Crypto.world

The Ledger

Ethereum Delays Glamsterdam’s Hoodi Upgrade Over Contract Risks

Ethereum has postponed Glamsterdam’s Hoodi testnet upgrade, which had been scheduled for October 26, 2026, while developers investigate EIP-8037’s interactions with mainnet smart contracts. No replacement Hoodi activation date or mainnet date has been announced.

Ethereum Delays Glamsterdam’s Hoodi Upgrade Over Contract Risks

Four days before Hoodi’s scheduled fork

Ethereum developers have postponed Glamsterdam’s Hoodi testnet upgrade, removing a fork that had been scheduled for October 26. The Ethereum Foundation announced the decision on October 22, saying developers need more time to investigate how EIP-8037 interacts with smart contracts on mainnet. No replacement activation date has been set.

The decision also cancels Hoodi’s planned gas-limit increase to 200 million at the upgrade epoch. Developers have removed the October 26 activation from the network configuration; the Foundation says the change does not roll back Hoodi’s existing chain history.

EIP-8037 puts gas assumptions under review

The postponement follows scrutiny of Glamsterdam’s gas-accounting changes. The agenda for the October 22 All Core Devs – Execution call listed security concerns around EIP-8037 and EIP-8038, along with the Hoodi fork and possible mainnet dates. The Foundation’s announcement specifically cites further investigation of EIP-8037’s interactions with mainnet contracts as the reason for delaying the testnet upgrade.

A ChainSecurity analysis published October 13 describes how the proposals could affect contracts that use gas checks or rely on a failed call leaving too little gas for a failure handler to finish. Under the proposed accounting, gas available after a failed call can differ from what existing code expects. ChainSecurity warns that some failure-handling paths may complete where they previously reverted, potentially changing contract behavior without any change to the contract’s code.

The analysis identifies risks in specific gas-checking assumptions, not a demonstrated attack on Ethereum or a confirmed exploit of a named application. The Foundation’s stated reason is to investigate EIP-8037’s interaction with mainnet contracts; it does not name affected protocols or say that developers have confirmed a vulnerability.

Hoodi operators must check client instructions

The Foundation tells Hoodi node and validator operators to check both execution- and consensus-layer client instructions before October 26. Earlier client releases that supported the scheduled fork should not be assumed to remove it: the Foundation says operators need releases whose notes explicitly confirm the old activation has been unscheduled. Custom network configurations that still target the October 26 fork also need to be updated.

The Foundation’s postponement page lists Lodestar v1.50.1 and Besu 26.10.1 as releases incorporating the change. It says additional client releases and builder or validator tooling guidance will be added as teams confirm them. The earlier Glamsterdam release table is not confirmation that a client has incorporated the postponement.

No mainnet date comes with the delay

Glamsterdam combines changes to Ethereum’s execution and consensus layers, including enshrined proposer-builder separation and block-level access lists. Hoodi was intended to test the upgrade after its October 6 activation on Sepolia. With Hoodi’s date now unset, the testnet schedule has changed, but the Foundation has not announced a new timeline for that test or for mainnet.

The update applies to Hoodi, not Ethereum mainnet. The Foundation says mainnet users and ETH holders do not need to take action because of the postponement; developers should not plan Hoodi testing around the canceled October 26 activation.

Sources

  1. Original source · Blog post Ethereum Foundation Blog blog.ethereum.org

Other pages read

  1. Ethereum GitHub github.com
  2. ChainSecurity chainsecurity.com

Related stories

Explore

More articles