EIP-8037/EIP-8038 Glamsterdam

59Importance
no updates 6h+Status
8News media
Published
Updated

Ethereum developers have paused the Glamsterdam step on the Hoodi testnet after security reviews flagged eight smart-contract assumptions that could be broken by EIP-8037 and EIP-8038. The Ethereum Foundation has opened a review for developers and auditors while the mainnet timetable remains unset.

Key claims & sources

✓
Chainsecurity found projects that could be vulnerable after Glamsterdam because they rely on invariants that EIP-8037 and EIP-8038 change.
✓
EIP-8037 and EIP-8038 rework how gas is charged for certain operations and for state.
✓
The Hoodi testnet upgrade remains paused, and no mainnet activation date has been confirmed.
✓
On November 6, 2026, the Ethereum Foundation asked smart-contract developers and auditors to test projects against eight gas-related assumptions that the proposed changes could break.
✓
Ethereum developers have delayed the Glamsterdam upgrade on the Hoodi testnet after security researchers identified eight existing smart-contract assumptions that could become invalid under the proposed gas-accounting changes.

What it means

Smart-contract teams and auditors now have a concrete checklist: eight gas-related assumptions published by the Ethereum Foundation that projects must test their code against before the fork resumes. Contracts with fixed gas budgets or reserves, the pattern most findings involve, may behave differently after the upgrade even without any code change on their end. Until audits clear these cases, the Hoodi step stays paused and no mainnet date can be set, leaving deployment teams waiting.

A protocol that changes how gas is priced can quietly invalidate contracts that never asked to be touched, which is why several developers pushed back hard. The Curve Finance founder's public plea, 'please don't break the chain,' captures the real tension: optimizing gas accounting at the protocol layer collides with the promise that deployed, immutable contracts keep working as written. Ethereum has resolved this before through delay and patching, not through forcing contracts to adapt.

The next checkpoint is whether audits against the eight published invariants clear the flagged projects, at which point developers can resume the Hoodi testnet step that was paused on November 6. A clean pass would let core developers set a mainnet activation date for Glamsterdam; fresh vulnerabilities would extend the pause further and could force changes to EIP-8037 or EIP-8038 themselves before any date is named.

Market reaction i

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

Ethereum fell 0.4% in the 4 hours after the first headline, after rising 0.4% in the 2 hours before.

$2,235 price at the headline
+0.4% 2 h before
-0.4% 4 h after
-0.3% 12 h after
First headline

47 prices, one every 30 minutes · The move was larger before the first headline than after: an observation, not an explanation. The market also moves on things nobody publishes.

Coverage timeline

Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.

first
Nov 6 10:15
Ethereum Foundation blog scoop our clock
Breaks the event
+12 min
Nov 6 10:27
The Defiant context
Its angle: reserves, defiant, involve
+3 h 7 m
Nov 6 13:23
+3 h 17 m
Nov 6 13:32
MEXC context
Its angle: announcement, postponement, repository
+3 h 53 m
Nov 6 14:09
crypto.news echo
No new facts: invalid, emerge, become
+5 h
Nov 6 15:16
Crypto Economy echo
No new facts: vulnerabilities, implementation, highlighted; with quotes
+1 d 5 h
Nov 7 16:00
NewsBTC echo
No new facts: compatibility, transactions, functioning; with quotes
+2 d 1 h
Nov 8 11:18
BeInCrypto context
Its angle: methodological, transaction, deployment; with quotes