Ethereum core developers postponed Glamsterdam’s implementation on the Hoodi testnet until security concerns involving eight smart contract invariants are resolved, according to a Cointelegraph report published on Nov. 6, 2026, at 21:23:08 UTC+8.
Why the gas changes raised concerns
The Ethereum Foundation said in a Friday blog post that some existing Ethereum projects depend on assumptions about how much gas certain operations cost. Glamsterdam’s EIP-8037 and EIP-8038 would change how gas is charged for certain operations, invalidating those assumptions.
The decision followed an Oct. 13 report from smart contract auditor ChainSecurity. Its findings indicated that the two Ethereum Improvement Proposals could break contracts that rely on fixed gas-related assumptions when external calls fail. The concern is therefore about compatibility with existing contract behavior—not a reported exploit.
What the delay means for the rollout
Postponing the Hoodi fork gives developers more time to identify potential contract issues and determine whether changes are necessary before Glamsterdam advances toward mainnet deployment. The Ethereum Foundation said the Hoodi fork would not proceed until the issues were resolved.
Glamsterdam had already gone live on the Sepolia testnet on Oct. 6, in one of its final major rehearsals. That testnet deployment was not a mainnet launch.
In a Sept. 28 blog post, the Foundation described Glamsterdam as advancing Ethereum’s layer-1 scaling roadmap through enshrined proposer-builder separation, block-level access lists and gas-pricing changes intended to better reflect execution costs.