Ethereum Delays Glamsterdam on Hoodi While Developers Investigate Contract Risks

Ethereum developers are holding off on the Glamsterdam upgrade’s Hoodi testnet fork while they investigate how two proposed changes, EIP-8037 and EIP-8038, could affect existing smart contracts. The Ethereum Foundation says security researchers at ChainSecurity found projects that may be vulnerable because the changes break assumptions—known as invariants—that those contracts rely on.

The proposed EIPs rework how much gas certain operations cost. Gas is the fee measure for using Ethereum’s computing resources, so changing those costs can affect not only transaction prices but also contracts that assume an operation will fit within a particular gas budget.

What risks are developers investigating?

The concern centers on eight smart contract invariants tied to EIP-8037 and EIP-8038. The Foundation’s description says ChainSecurity identified projects that could be vulnerable after Glamsterdam because they rely on assumptions the proposals would change. The reports provided here do not name those projects or detail the specific failure modes.

This is a testnet issue, not an announcement that Glamsterdam has been activated on Ethereum’s main network. Developers are investigating the risks before proceeding with the Hoodi fork, and no replacement date is specified in the available information.

What does the Hoodi delay mean for contract users?

For everyday users, the immediate point is that the upgrade is still being tested and developers have surfaced a compatibility concern before moving ahead. A contract that depends on an assumption about gas costs could behave differently after a change, though the source does not say that funds have been lost or that every contract is affected.

This follows an earlier Glamsterdam Hoodi test delay after researchers raised concerns that new gas rules could cause some contracts to record failed operations. The current investigation adds a more specific scope—eight invariants linked to EIP-8037 and EIP-8038—rather than announcing a confirmed exploit. The earlier Hoodi test delay offers context, but the new question is whether developers can resolve or work around the identified dependencies before rescheduling the fork.

What should developers and users watch next?

The next meaningful update is whether Ethereum’s developers and security researchers can identify affected contracts and determine how to address the invariant breaks. Until a new Hoodi activation date and a mitigation plan are announced, developers should avoid assuming the previous test schedule is still current. The available reporting does not specify a mainnet date or a required action for ordinary ETH holders.