Ethereum developers are keeping the planned Glamsterdam upgrade off the Hoodi testnet schedule while auditors examine whether proposed gas-accounting changes could alter the behavior of deployed smart contracts. In an update dated November 9, the Ethereum Foundation said it had received four reports identifying deployed contracts that could break under proposals EIP-8037 and EIP-8038. Those are potential compatibility failures under review, not four confirmed exploits or losses.
The review is unusually consequential because the problem is not limited to brand-new applications. Some existing, immutable contracts were designed around assumptions about what operations cost and how much gas remains available during execution. A protocol upgrade that changes those assumptions can make an old contract behave differently even when its published code has not changed.
Why EIP-8037 and EIP-8038 created concern
The two proposals modify how Ethereum charges for certain operations and for state-related activity. Those changes are intended to better align network fees with resource use, an important element of scaling. But economic accounting rules can become part of application logic. For example, a contract may depend on whether a transaction has enough gas to complete a downstream step. A seemingly reasonable change to the charge for that step can invalidate the assumption.
The Ethereum Foundation says ChainSecurity originally identified applications that could rely on invariants the proposals would break. Its latest update urges application teams and auditors to examine those invariants and submit concrete examples. Developers are also prototyping possible specification revisions, though none has been selected or committed for activation.
The next dates are for audits, not a mainnet launch
The foundation’s published sequence points to audit findings from ChainSecurity and Dedaub on November 13, a developer and auditor discussion on November 16, and an AllCoreDevs execution call on November 19. It explicitly says no decision has been pre-committed for that final meeting. A previously targeted October 26 Hoodi activation was postponed; there is still no replacement Hoodi time in the current notice.
This is a testnet scheduling and compatibility matter. It does not mean Ethereum mainnet has suffered an exploit, and the foundation has not instructed ordinary ETH holders to move assets because of the review. Developers should instead check whether their applications depend on the listed gas or state invariants before assuming they will remain unaffected.
A broader lesson about blockchain upgrades
Protocol upgrades can improve throughput and fee models while placing the burden of compatibility on projects that have already deployed permanent code. That tension is one reason real-world testing matters. Optimisus has previously covered how cross-chain messaging requires operational integration beyond a working bridge and how application assumptions can become a source of security exposure.
The next meaningful update will be evidence from the audits and whether Ethereum’s developers preserve, modify, or drop the contested changes. Until those decisions are published, announcing a new Hoodi or mainnet activation date would be premature.
Primary sources: Ethereum Foundation’s November 6 post, updated November 9; Hoodi postponement and operator notice.
