Ethereum core developers delayed the Glamsterdam upgrade’s deployment on the Hoodi testnet pending resolution of security concerns involving eight smart contract invariants, according to an Ethereum Foundation blog post cited by Cointelegraph.
The report was published on Nov. 6, 2026, at 21:23:08 UTC+8. At that time, the Foundation said the Hoodi fork would not proceed until the issues were resolved.
Why the gas changes raised concerns
Some existing Ethereum projects depend on assumptions about how much gas particular operations cost. According to the Foundation, Glamsterdam’s EIP-8037 and EIP-8038 would invalidate certain assumptions by changing how gas is charged for some operations.
The decision followed an Oct. 13 report by smart contract auditor ChainSecurity, which found that the two proposals could break contracts that rely on fixed gas-related assumptions when external calls fail. The reported concern was potential contract breakage, not evidence that such failures had occurred on Ethereum mainnet.
What the delay means for the upgrade
Postponing the Hoodi fork gives developers more time to identify potentially affected contracts and determine whether changes are needed before Glamsterdam moves toward mainnet deployment. The report did not provide a replacement date for the Hoodi rollout.
Glamsterdam had already gone live on the Sepolia testnet on Oct. 6, described in the report as one of its final major rehearsals. That testnet activation did not mean the upgrade had been activated on mainnet.
In a Sept. 28 blog post, the Foundation said Glamsterdam aims to advance 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.