A supplied report says the Ethereum Foundation asked contract developers and auditors to determine whether their projects rely on eight gas-billing assumptions that Glamsterdam would alter through EIP-8037 and EIP-8038. Separately, Ethereum Foundation and All Core Devs snippets indicate that the Hoodi testnet activation previously scheduled for October 26, 2026 was postponed as developers investigate EIP-8037 interactions with mainnet smart contracts.

What EIP-8037 and EIP-8038 will change

The clearest available explanation is that Glamsterdam will reprice two distinct categories of EVM operations. An Ethereum Foundation blog snippet says EIP-8037 raises and separately meters the cost of creating state, while EIP-8038 updates the cost of accessing existing state.

This is more specific than a broad warning about “gas changes.” According to the same snippet, EIP-8037 covers new accounts, new storage slots, and deployed bytecode. EIP-8038 is described as changing state-access costs for operations including SSTORE, SLOAD, cold account access, EXTCODESIZE, and EXTCODECOPY.

The supplied report links these repricings to eight gas-billing assumptions that developers and auditors have been asked to review. It also says the Ethereum Foundation created a repository containing explanations, examples, and self-check keywords for each assumption, and that affected projects can contact the team. The exact eight-item checklist is not included in the supplied material. For now, the narrower practical conclusion is that code relying on older gas-cost behavior for state creation or state access is the reported focus of review.

Why Hoodi was postponed and what changed

The previously announced Hoodi rollout plan was subsequently withdrawn. An Ethereum Foundation blog snippet says Glamsterdam had been scheduled to activate on Hoodi on October 26, 2026 at 17:42:48 UTC, at epoch 132,352 and slot 4,235,264. Hoodi's gas limit was also due to increase to 200M in the same epoch.

A later Foundation snippet says core developers decided at ACDE #248 to delay the Hoodi activation so they could further investigate EIP-8037 interactions with mainnet smart contracts. It adds that the delay removed the scheduled Amsterdam execution-layer activation, the Gloas consensus-layer activation, and the related Hoodi gas-limit schedule.

An ethereum/pm GitHub snippet provides another concrete status update: scheduling for the Hoodi fork implementing EIP-8037 and EIP-8038 was delayed by at least two weeks and would be reconsidered after audits were completed. This does not establish a new activation date. It does clarify the current position: the October 26 Hoodi plan is no longer active, and the next reported milestone is further compatibility work and completion of the audits.

What developers should take from the current guidance

The message for developers is not that every Ethereum contract is expected to fail. Rather, the supplied report presents this as a targeted self-review for projects whose logic may depend on gas-billing assumptions that will no longer apply after Glamsterdam reprices state creation and state access.

The scope also appears to extend beyond deployed Solidity contracts. The report says the Foundation cannot cover every Ethereum project and all associated on-chain and off-chain code. That matters for teams operating relayers, automation, monitoring, or other software that assumes particular execution-cost behavior. Until Hoodi is formally rescheduled, the most concrete action indicated by the available information is a compatibility review rather than calendar planning.