Ethereum developers have officially decided to postpone the highly anticipated Glamsterdam hard fork on the Hoodi testnet following the identification of critical, gas-related security risks. These vulnerabilities could fundamentally alter how existing smart contracts handle failed transactions, posing unforeseen dangers to decentralized applications across the ecosystem.
The Ethereum Foundation (EF) announced that the upgrade, which was originally scheduled to go live on October 26, would be delayed indefinitely. This pause will give core developers and security researchers adequate time to thoroughly investigate how several proposed changes interact with smart contracts already deployed on the Ethereum mainnet.
The security concerns first came to light on October 13, when blockchain security firm ChainSecurity published an advisory warning that two specific proposals included in the Glamsterdam upgrade—designated as EIP-8037 and EIP-8038—could inadvertently weaken crucial safeguards against a specific type of malicious behavior known as insufficient gas griefing.
This unexpected postponement has naturally cast a shadow of uncertainty over the broader timeline for Glamsterdam’s eventual mainnet rollout. Prior to these security discoveries, Ethereum developers had been actively considering an early December launch date, with tentative plans to finalize a rigid schedule only after observing a successful deployment and testing phase on the Hoodi testnet. With the Hoodi rollout now on hold, that timeline is effectively back to the drawing board as the community prioritizes network safety above speed.
Gas Changes Could Undermine Existing Smart Contract Safeguards
In its detailed technical analysis, ChainSecurity explained that under the newly proposed upgrade rules, unspent gas could potentially be returned to a smart contract immediately after an operation fails. This shift would allow the contract to continue executing subsequent code in circumstances where it previously would have halted entirely. The security researchers pointed out that these subtle changes could severely interfere with existing, time-tested security checks that rely heavily on monitoring exactly how much gas remains available during the execution of a transaction.
In attacks commonly referred to as insufficient gas griefing, a malicious caller deliberately provides just enough—or rather, too little—gas for a legitimate smart contract operation to successfully complete its intended state changes. ChainSecurity warned that Glamsterdam’s proposed modifications could undermine the foundational safeguards that protect protocols against such tactics. By altering how failures and remaining gas are handled, the upgrade could potentially allow contracts to permanently record failed operations as if they were handled differently, corrupting expected application states.
For example, a vulnerable and affected contract might prematurely remove a user’s pending claim or permanently disable the user interface option to retry the failed transaction. This would leave everyday users entirely unable to complete an otherwise valid and legitimate financial operation, resulting in locked funds or broken application logic through no fault of the user.
ChainSecurity was careful to note that the Glamsterdam upgrade would not render all gas-related security checks completely unreliable across the board. Certain safeguards and assertions would likely continue to function as intended, but developers across the ecosystem would still need to meticulously review their codebase to ensure their smart contracts properly account for the upgrade’s novel gas accounting rules.
These alarming findings quickly prompted widespread concern among key Ethereum contributors and protocol engineers. Weighing in on an ongoing GitHub discussion thread on October 21, pseudonymous security researcher pcaversaccio described the identified risks as deeply serious and publicly called for an immediate reassessment of the hard fork parameters and its overarching trajectory.
Adding to the urgency, ChainSecurity revealed that it had successfully identified 13 real-world examples of vulnerable patterns in existing codebases and was actively coordinating responsible disclosure processes with the affected project teams. While the security firm chose not to publicly disclose specific technical details regarding the 13 real-world examples, nor identify the specific decentralized finance projects involved, they strongly urged all smart contract developers to audit their contracts as soon as possible.
These fresh security concerns directly follow an earlier warning issued by the Ethereum Foundation, which cautioned that Glamsterdam’s revised gas model could potentially break various developer tools, third-party wallets, blockchain indexers, and gas estimation utilities that rely heavily on fixed historical assumptions about the network. Prior to the Hoodi testnet delay, the Glamsterdam upgrade had already been successfully activated on the Sepolia testnet on October 6, demonstrating that testnet deployments were actively underway before the deeper security implications came to light.
