Ethereum developers have officially decided to postpone the deployment of the upcoming Glamsterdam hard fork on the Hoodi testnet. The decision comes in the wake of newly identified gas-related security risks that have the potential to severely alter how existing smart contracts handle failed transactions, introducing complex vulnerabilities into the decentralized ecosystem.
The Ethereum Foundation (EF) announced that the upgrade, which was originally scheduled to take place on October 26, would be delayed indefinitely. According to the foundation, this precautionary pause will allow core developers and security researchers adequate time to thoroughly investigate how several key upgrade proposals interact with already deployed smart contracts operating on the Ethereum network.
The security concerns were initially brought to light on October 13 by blockchain security firm ChainSecurity. In a detailed advisory, the firm warned that two specific proposals integrated into the Glamsterdam upgrade—designated as EIP-8037 and EIP-8038—could inadvertently weaken critical safeguards protecting the network against a sophisticated attack vector known as insufficient gas griefing.
This unexpected postponement has inevitably cast a shadow of uncertainty over the broader mainnet timeline for Glamsterdam. Prior to the discovery of these vulnerabilities, Ethereum developers had been actively considering an early December target for the mainnet rollout, with the definitive schedule contingent upon the successful completion and observation of testing phases on the Hoodi testnet.
Gas Changes Could Undermine Existing Smart Contract Safeguards
At the heart of the controversy is a fundamental shift in how gas is managed and returned during execution failures. In its comprehensive analysis, ChainSecurity explained that under the modified rules introduced by the upgrade, gas could potentially be refunded to a contract following an operation failure. This behavioral shift could allow a contract to continue running its execution flow in scenarios where it otherwise would have immediately halted and terminated under current network rules.
Researchers pointed out that these changes directly interfere with existing security checks that rely heavily on precise calculations of how much gas remains available during the lifecycle of a transaction. For years, smart contract developers have built defensive programming patterns based on deterministic gas consumption models.
In attacks known as insufficient gas griefing, a malicious caller deliberately provides just enough—or rather, too little—gas for a legitimate smart contract operation to succeed, while still forcing state changes or consuming computational overhead. ChainSecurity warned that Glamsterdam’s proposed modifications could actively undermine established safeguards against such malicious actions.
By altering the point of failure and gas retention, the upgrade could potentially allow contracts to permanently record failed operations under false pretenses. For instance, an affected decentralized application contract could inadvertently remove a user’s legitimate claim or permanently disable the option to retry a failed transaction. This would leave everyday users stranded, completely unable to complete an otherwise valid and necessary financial or operational interaction on the blockchain.
Importantly, ChainSecurity clarified that the Glamsterdam upgrade would not render all gas-related security checks completely unreliable across the board. Certain foundational safeguards could theoretically continue to function as intended. However, the catch is that developers would still be forced to conduct exhaustive code reviews of their entire protocol suites to ensure they properly account for the upgrade’s novel gas rules and edge cases.
The alarming findings quickly prompted widespread concern among the broader community of Ethereum contributors and core protocol developers. Weighing in on the discussion on October 21 via GitHub, pseudonymous security researcher pcaversaccio described the identified risks in stark terms, categorizing them as "serious" and formally calling for a deep reassessment of the hard fork’s trajectory and contents.
Adding urgency to the situation, ChainSecurity revealed late last week that its ongoing audits had successfully uncovered "13 real-world examples" of vulnerable contracts in the wild. The security firm noted that it was actively coordinating responsible disclosure efforts with the various affected projects to help them mitigate the risk before any mainnet activation occurs.
While ChainSecurity opted not to publicly disclose specific technical details of the 13 real-world examples, nor identify the specific decentralized finance projects or protocols involved, the firm issued a stern advisory urging all developers to inspect their smart contract codebases as soon as possible.
These latest revelations compound an already mounting list of compatibility warnings surrounding the upgrade. Earlier, the Ethereum Foundation had already issued a separate public advisory warning that Glamsterdam’s overarching gas model overhaul could potentially break various developer tools, including downstream wallets, blockchain indexers, and gas estimation utilities that rely heavily on fixed assumptions about how the Ethereum Virtual Machine handles execution costs and gas refunds.
The Glamsterdam upgrade cycle has already seen several milestones, having been successfully activated on the Sepolia testnet earlier this month on October 6. However, the unexpected friction encountered on the path to the Hoodi deployment demonstrates the delicate and intricate nature of upgrading a multi-billion-dollar decentralized network without disrupting the vast web of smart contracts built upon it.
