Reporting: sourced factual coverage reviewed by the editorial desk.
Ethereum core developers are holding back the Glamsterdam fork on the Hoodi test network after testing exposed risks for some existing smart contracts. The Ethereum Foundation disclosed the decision on November 6 and asked developers and auditors to check their software before the upgrade advances.
The concern is how contracts behave when an operation fails. Gas measures the resources an Ethereum transaction uses. Some contracts rely on how much gas is available after a call fails to decide whether to reverse the whole operation or continue. Glamsterdam would change how the network prices access to stored data and charges for adding new data. ChainSecurity, which researched the issue, found that those changes could allow some failure handlers to finish in cases where they previously would have reverted. An operation that could previously be retried might instead be recorded as a permanent failure.
The Foundation says the upgrade is still being tested on test networks. Its November 6 notice describes risks that could arise after Glamsterdam and does not report a mainnet exploit. The Foundation is working with ChainSecurity and Dedaub and doing internal audits. It also published a checklist of eight assumptions for teams to review, because the auditors cannot cover every project’s on-chain and off-chain code.
For teams running payments, token transfers or other automated workflows on Ethereum, the practical question is whether their existing failure handling still works after the repricing. The Foundation says work on Hegota, the next upgrade after Glamsterdam, continues in parallel. It did not give a new Hoodi date in the notice.


Join the conversation
Share your perspective and reply to other readers in Community.
Discuss this article →