Skip to main content
Blockchain Today

Crypto markets, protocols and policy

Ethereum puts Glamsterdam on hold over gas-accounting risks

Ethereum has paused Glamsterdam’s Hoodi rollout while developers review eight gas assumptions affected by EIP-8037 and EIP-8038; no new date is set.

By Blockchain Today Editorial3 min read

Ethereum puts Glamsterdam on hold over gas-accounting risks

Ethereum’s developers have paused Glamsterdam’s Hoodi testnet rollout while they investigate how two proposed gas changes could affect existing smart contracts. In a November 6 post, the Ethereum Foundation said All Core Developers had decided not to fork Hoodi until the issues are resolved, and asked contract developers and auditors to check eight assumptions the upgrade would change.

The pause follows an earlier schedule change: Hoodi’s upgrade, set for October 26, was postponed on October 22, with no replacement date. The latest post describes why the review is continuing. It does not say eight contracts have been found vulnerable; the Foundation says a few projects have been identified so far, while the eight items are gas-related invariants for developers to examine.

What changes in EIP-8037 and EIP-8038?

EIP-8037 changes the cost of creating blockchain state and introduces a separate reservoir for state gas; EIP-8038 reprices state access. Together, they alter how much gas operations consume and how much gas may remain available after a failed call. The proposals are part of Glamsterdam, Ethereum’s next upgrade, which is being tested on testnets.

That accounting matters when a contract calls another contract and then handles a failure. Some code checks the remaining gas to decide whether the call ran out of gas, or depends on the failure handler itself running out of gas so the whole operation reverts. ChainSecurity’s October 13 analysis describes how the new accounting can return gas after a failed call or let state-writing code complete with less execution gas than before. In those cases, a contract might record a permanent failure where it previously reverted and left room to retry.

The Foundation’s eight-invariant review repository broadens the checklist beyond those failure paths. It flags hard-coded gas budgets, gas reserves sized for current costs, calculations that assume gas can only decrease, and assumptions about EIP-7702 wallet delegations. The repository says the most common findings so far concern fixed gas budgets and reserves; it does not name affected projects.

How does the delay change the upgrade plan?

Hoodi will not follow the October 26 schedule, and the Foundation has set no replacement activation date. The October postponement removed both the Amsterdam execution-layer and Gloas consensus-layer activations from Hoodi’s configuration, along with a planned increase in its gas limit to 200 million. The Foundation says the delay concerns Hoodi and does not set a mainnet date; it also said mainnet users and ETH holders need take no action as a result of that schedule change.

The trade-off is time for contract teams and auditors to test failure paths against the proposed gas rules, at the cost of delaying a testnet milestone. Developers are also considering whether specification changes could prevent the reported issues. The Foundation says work on Hegota, the following upgrade, continues in parallel and is unaffected.

What should developers watch next?

The immediate signal is what developers and auditors find when they check both on-chain contracts and off-chain systems that rely on gas estimates. The Foundation says it is working with ChainSecurity and Dedaub and conducting internal audits, while acknowledging that it cannot review every project and its supporting infrastructure. It asks affected teams to report findings to the Foundation so they can inform discussion at upcoming All Core Developers calls.

Those reviews will help determine whether EIP-8037 or EIP-8038 needs adjustment before Glamsterdam proceeds. Until developers publish a revised Hoodi schedule, the testnet activation date remains unset; the mainnet timing remains unconfirmed.

Sources and documents