Ethereum Foundation Calls for Contract Checks After Glamsterdam Security Findings
Most findings involve fixed gas budgets and reserves. The Hoodi testnet upgrade remains paused, with no confirmed mainnet activation date.
TL;DR
Ethereum postponed the Glamsterdam hard fork on the Hoodi testnet after ChainSecurity identified eight smart‑contract invariants at risk from gas‑pricing changes in EIP‑8037 and EIP‑8038. The delay gives developers time to audit and fix vulnerable contracts before the upgrade proceeds.
Key facts
- The Hoodi testnet fork was scheduled for Oct. 26 at 17:42:48 UTC.
- ChainSecurity’s Oct. 13 report highlighted eight smart‑contract invariants at risk.
- The report cited 13 real‑world examples of potentially vulnerable projects.
- EIP‑8037 and EIP‑8038 change gas charging for state creation and access operations.
- The planned gas‑limit increase to 200 million was removed from Hoodi’s schedule.
The Ethereum Foundation announced on November 6 that the Glamsterdam hard‑fork on the Hoodi testnet has been postponed. The decision follows a security review by blockchain auditor ChainSecurity, which flagged compatibility and gas‑related risks in two proposals, EIP‑8037 and EIP‑8038. Foundation researcher Toni Wahrstätter posted the delay on X, noting that core developers voted to hold the upgrade until the identified eight smart‑contract invariants are examined. The postponement pushes back the originally scheduled Hoodi activation on Oct. 26 and adds uncertainty to the timeline for Glamsterdam’s mainnet launch.
Background
Glamsterdam is the next major network upgrade in Ethereum’s roadmap, aiming to improve layer‑1 scaling through proposer‑builder separation, block‑level access lists and revised gas‑pricing mechanisms. The upgrade was first activated on the Sepolia testnet on Oct. 6, providing a final major testing stage before moving to Hoodi, the testnet slated for a hard fork on Oct. 26. The upgrade includes two gas‑related proposals, EIP‑8037 and EIP‑8038, which modify how gas is charged for state creation and access operations. ChainSecurity, a security firm that audits smart contracts, issued an Oct. 13 report warning that the new gas rules could break contracts that rely on fixed gas‑cost assumptions, especially when external calls fail. The report identified eight smart‑contract invariants that could be violated, and cited 13 real‑world examples of projects potentially affected. Ethereum’s All Core Developers (ACD) group, which coordinates hard‑fork decisions, responded by pausing the Hoodi fork and calling on developers and auditors to review their code. The Foundation also published a public repository documenting the eight invariants and encouraging community participation. Meanwhile, work on the subsequent Hegota upgrade continues unaffected.
What happened
On Oct. 13 ChainSecurity released an analysis that highlighted gas‑related security risks in EIP‑8037 and EIP‑8038, noting that the proposals could weaken safeguards against insufficient gas griefing attacks. The firm said the changes might allow contracts to continue executing after a failed external call, breaking assumptions that gas consumption only moves in one direction. ChainSecurity reported eight smart‑contract invariants at risk and referenced 13 real‑world examples, though it did not disclose the projects involved. On Oct. 21 a pseudonymous researcher, pcaversaccio, posted a GitHub comment describing the risks as “serious” and urging a reassessment. The Ethereum Foundation responded on Oct. 26 when researcher Toni Wahrstätter announced on X that core developers had decided to postpone the Glamsterdam upgrade on the Hoodi testnet. The Foundation’s blog post on Nov. 6 reiterated the pause, explaining that developers need more time to identify vulnerable contracts and determine whether protocol‑level adjustments are required. The decision also removed the Amsterdam execution‑layer activation, the Gloas consensus‑layer activation and the planned gas‑limit increase to 200 million from Hoodi’s schedule. The upgrade remains active on Sepolia, and testing continues on other networks while the Hoodi fork stays on hold pending further audits and community review.
Market impact
The sources do not provide direct price data, but they do mention several quantitative details that could influence market sentiment. The Hoodi fork was originally set for Oct. 26 at 17:42:48 UTC, and its delay removes the scheduled gas‑limit raise to 200 million, a figure that had been part of the upgrade’s performance expectations. ChainSecurity’s report cited eight smart‑contract invariants and 13 real‑world examples of potentially vulnerable projects, prompting developers to audit their codebases. The postponement adds uncertainty to the timeline for Glamsterdam’s mainnet deployment, which may affect investor confidence in Ethereum’s scaling roadmap. Ongoing testing on Sepolia and other networks continues, but the lack of a new Hoodi date leaves the market without a clear short‑term upgrade milestone.
Why it matters
The delay matters because Glamsterdam’s gas‑pricing changes are central to Ethereum’s scaling strategy. If contracts that depend on fixed gas assumptions break, users could lose the ability to retry transactions or see permanent failures recorded, undermining trust in the platform’s reliability. The identified eight invariants touch on fundamental contract logic, such as assumptions about gas consumption direction and fixed gas allowances. By pausing the Hoodi fork, the Foundation gives developers time to audit and potentially patch vulnerable contracts, reducing the risk of widespread failures after the upgrade goes live. The postponement also signals to the broader ecosystem that security reviews are a priority, which may encourage more rigorous testing of future proposals like Hegota. However, the uncertainty around the mainnet rollout could slow adoption of scaling improvements and affect projects that were counting on the new gas model to reduce costs. Overall, the decision reflects a trade‑off between rapid deployment and preserving the stability of the existing contract ecosystem.
DeFi Intel’s take
Editorial analysis, not a statement of fact.
DeFi Intel's take: the postponement suggests that the Ethereum community is willing to sacrifice short‑term upgrade momentum to avoid systemic contract failures. The eight identified invariants indicate that a non‑trivial portion of on‑chain applications could be exposed to new gas‑related edge cases, so the call for broad auditor participation is prudent. We read this as a signal that future upgrades may undergo even tighter pre‑deployment scrutiny, especially when they alter core execution economics. While the delay adds uncertainty to the Glamsterdam timeline, it also reinforces confidence that the network will not rush potentially disruptive changes onto mainnet.
Sources used for this analysis
- en.bloomingbit.io/feed/news/122943
- tradingview.com/news/cointelegraph:03940a310094b:0-ethereum-delays-glamsterdam-hoodi-testn
- kucoin.com/news/flash/ethereum-devs-delay-glamsterdam-hoodi-fork-over-smart-contract-risks
- newscord.org/article/ethereum-core-developers-delay-glamsterdam-hoodi-fork-over-eight-smar
- crypto.news/ethereum-delays-glamsterdam-upgrade-as-eight-smart-contract-risks-emerge/
DeFi Intel wrote this analysis from the reporting above. Any figure or quotation can be checked against those pages.
Frequently asked questions
What caused the Glamsterdam upgrade to be delayed on the Hoodi testnet?
The delay was caused by a security review from ChainSecurity that identified compatibility and gas‑related risks in EIP‑8037 and EIP‑8038. The review highlighted eight smart‑contract invariants that could be broken, prompting core developers to postpone the Hoodi fork until the issues are addressed.
Which proposals are at the center of the identified risks?
The proposals are Ethereum Improvement Proposals EIP‑8037 and EIP‑8038. Both modify how gas is charged for certain state‑creation and access operations, and the changes could affect contracts that rely on fixed gas‑cost assumptions, especially during failed external calls.
What actions has the Ethereum Foundation taken after the findings?
The Foundation published a GitHub repository documenting the eight affected invariants, issued a public call for developers and auditors to review their contracts, and announced that the Hoodi hard fork will remain on hold until the identified concerns are resolved.
Direct answers
Short answers, written to be quoted.
- Why did Ethereum delay the Glamsterdam upgrade on Hoodi?
- Ethereum delayed the upgrade because ChainSecurity identified eight smart‑contract invariants that could be broken by the gas‑pricing changes in EIP‑8037 and EIP‑8038, prompting a pause for further review.
- What are the main concerns with EIP‑8037 and EIP‑8038?
- The main concerns are that the proposals alter gas accounting for state creation and access, potentially breaking contracts that rely on fixed gas‑cost assumptions and weakening safeguards against insufficient gas griefing attacks.
- What steps is the Ethereum Foundation taking after the security findings?
- The Foundation published a repository of the eight affected invariants, called on developers and auditors to review their code, and announced that the Hoodi hard fork will stay on hold until the issues are resolved.
DeFi Intel is an entity-graph aggregator: we curate, tag and link crypto news to a typed knowledge graph of protocols, tokens, people and incidents. We do not republish the full article body. Use the link above to read the original report at The Defiant.
Entities in this story
Discussion
Comments are reviewed before publication.
Want the full article?
Continue reading on The Defiant →
No comments yet.