EIP-8037/EIP-8038 Glamsterdam

Teams running contracts with fixed gas budgets or reserves now have to re-test against eight specific assumptions the Ethereum Foundation published on November 6, 2026, rather than wait for an audit cycle tied to a mainnet date. Multisig wallets, relayers and any system that hard-codes a gas stipend for sub-calls are the likely casualties if they skip this step. Auditors gain a concrete checklist; protocol teams lose the ability to treat Glamsterdam as a fixed-date release.

A contract that never changes its bytecode can still change its behavior once the gas rules underneath it move, which cuts against the assumption that deployed code is a fixed, auditable contract with the chain. That is a narrower version of the 2019 debate, but it recurs every time Ethereum adjusts opcode pricing: efficiency gains at the base layer can quietly invalidate security assumptions several layers up, and no amount of code review catches that unless the invariants are tested explicitly, as Chainsecurity's findings show.

The Hoodi testnet fork stays paused with no mainnet activation date confirmed, so the next marker is whether the Ethereum Foundation's eight-point review closes out the open invariants from the November 6 post. A clean resolution restarts the Hoodi schedule and puts a mainnet date back on the table; further vulnerable contracts surfacing would push EIP-8037 and EIP-8038 back for redesign rather than just more testing time.

EthereumETH it is the asset of the company or protocol in the event

The move was larger before the first headline than after. That is an observation, not an explanation: the market also moves on things nobody publishes.