Ethereum Faces Glamsterdam Gas-Rule Decision Thursday
- Published
- Updated
Ethereum core developers are set to decide on two gas repricing proposals on Thursday, with one estimate putting 10,000 to 15,000 deployed contracts at risk of being affected. Separately, developers will also discuss whether to change rules that can alter how existing contracts handle failed operations, while Glamsterdam’s activation on Hoodi stays on hold.
Key claims & sources
What it means
Ethereum core developers use EIPs to change how the network handles execution, and gas repricing touches the rules that contracts rely on when they run. A Thursday decision on EIP-8037 and EIP-8038 puts contract behavior under review at the protocol level, not just in application code. That makes the meeting relevant to teams that build on Ethereum as well as to people who already have contracts deployed there.
For contract deployers and developers, a change in gas rules can mean code that worked under one fee schedule or execution pattern needs to be checked again. The estimate that 10,000 to 15,000 contracts are exposed shows the review is not limited to a small corner of the network. If the rules move, builders may need to test existing deployments against the new behavior before relying on them.
Ethereum is still balancing protocol maintenance with backward compatibility, and that trade-off is visible in the discussion over failed operations and the pause around Glamsterdam on Hoodi. The network wants room to update execution rules, but every such change can reach contracts already live on chain. That tension matters because Ethereum’s reliability depends on preserving what already exists while still changing the base layer.
The open questions are whether the Thursday discussion turns into an accepted rule change and whether Glamsterdam’s paused activation on Hoodi gets a new schedule. It is also not clear from the available details which contracts would be affected in practice or how large the resulting behavior changes would be for users. Those answers would come from the developer decision and any later implementation notes on Hoodi.
Market reaction i
Ethereum rose 0.7% in the 4 hours after the first headline, after rising 0.8% in the 2 hours before.
42 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.
Has this happened before?
| When | What happened | Figure |
|---|---|---|
| 3 days ago | Vitalik Buterin backs Ethereum gas overhaul, proposes changes to airdrops event | 1 actors in common · 6 news media |
| 7 days ago | Ethlabs proposes faster Ethereum quantum upgrade over AI concerns event | 1 actors in common · 4 news media |
| 9 days ago | [ARFC] Repositioning Aave V3 Core Around Established & Liquid Collateral event | 1 actors in common · 3 news media |
| 14 days ago | [Constitutional] AIP: Approve Release of Frozen ETH and ARB event | 1 actors in common · 4 news media |
| 22 days ago | How Aave’s Variable Borrow Rate Changes an Existing USDT Loan event | 1 actors in common · 2 news media |