TLDR
Ethereum (ETH) core developers have warned that the Glamsterdam upgrades gas repricing could break a small group of Layer 1 smart contracts unless they are updated.
- The alert focuses on EIP-8037 and EIP-8038, which change state-creation and storage-access gas costs and can disrupt contracts that rely on fixed gas assumptions.
- Glamsterdam aims to scale Ethereum L1 with proposerbuilder separation and block-level access lists, while adjusting gas economics; most users should see smoother performance rather than dramatic changes.
- Builders and infrastructure providers now face a mandatory testing window on Glamsterdam testnets, with the main risk being unpatched contracts or wallets that mis-estimate gas when mainnet activation arrives.
Deep Dive
1. What Developers Are Warning About
Ethereum Foundation engineers have issued an alert that Glamsterdams gas repricing, via EIP-8037 and EIP-8038, can break or degrade a small set of mainnet Layer 1 contracts that assume old gas rules. Reports note that contracts using 2,300-gas stipends, hardcoded call limits, or gasleft-based logic are most exposed, while most other contracts remain unaffected after replay testing on the new schedule. Developers are urging teams to test immediately on the Platberget Glamsterdam devnet and update fixed gas assumptions, emphasising that many flagged failures can be fixed simply by raising transaction gas limits in affected paths, but that this must be done before mainnet goes live. This alert is framed as targeted, not a general panic: the goal is to catch edge cases early rather than suggest broad breakage across Ethereum.
2. Why Glamsterdam Matters For Ethereum
Glamsterdam sits in Ethereums post-Fusaka roadmap as a major base-layer upgrade focused on scaling and protocol housekeeping. Articles summarising the roadmap explain that Glamsterdam integrates enshrined proposerbuilder separation (ePBS) and block-level access lists to improve block building and enable more parallel transaction execution, while also repricing state storage and access to better reflect modern hardware costs. Over time, this is intended to support much higher block gas limits and throughput, and to lay groundwork for richer account abstraction features that improve wallet UX without sacrificing security. For regular users, the headline effects are likely to be more consistent fees and higher capacity, while most of the complexity is borne by node software, wallets, rollups, and contract developers.
3. What Builders And Users Should Watch Next
The immediate next steps are technical. Builders should test L1 contracts on Platberget and upcoming public testnets, update any hardcoded gas constants, and ensure their wallets, RPCs, and indexers adopt revised gas-estimation rules so transactions do not fail silently under Glamsterdam pricing. Roadmap pieces indicate Glamsterdam is targeted for a 2026 mainnet activation window, with forks on networks like Sepolia and Hoodi preceding the final deployment, so there is time but not room for complacency. For end users, the main risk is localized: specific applications whose teams do not upgrade may experience reverted transactions or odd behaviour around contract calls or new-account creation when Glamsterdam activates.
If you rely on Ethereum L1 apps, watch whether those projects publicly confirm Glamsterdam testing; robust communication here is a useful signal of operational maturity and lower upgrade risk.
Conclusion
The developer alert around Glamsterdam is not about Ethereum breaking broadly, but about tightening gas economics in ways that expose brittle, assumption-heavy contracts. As Glamsterdam moves from devnets to testnets and eventually mainnet, the upgrade should improve Ethereums throughput and fee predictability, provided infrastructure and contracts are updated in time. For crypto users and builders, the edge lies in tracking which teams treat this as a serious maintenance window, as their preparation will largely determine how smooth the next phase of Ethereums scaling journey feels in practice.
