Ethereum Developers Challenge Glamsterdam Gas Repricing Over Contract Risks

Why Glamsterdam’s gas proposal is under challenge

Ethereum’s planned Glamsterdam upgrade is facing calls from developers to pause in its current form. The immediate dispute concerns EIP-8037, a proposal to raise gas costs for creating new state, including storage entries and new contracts. Critics argue the change could affect existing applications as well as future deployments, making the proposal’s compatibility with already-deployed code a central issue for the upgrade’s design and review.

The technical concern is that some contracts specify a fixed amount of gas for particular operations or inspect how much gas remains during a transaction. If the relevant operations become more expensive under EIP-8037, those calls may no longer have enough gas to finish. That possibility is not a claim that every contract will fail; it is a warning that code relying on assumptions about gas costs could behave differently after the change.

The consequences could be unusually difficult to reverse for affected applications. Deployed smart contracts are immutable, so developers cannot simply edit the original code to accommodate higher costs. Critics warn that failed calls could leave funds held by some contracts inaccessible. The source does not establish which users or contracts would ultimately be affected, or whether a fix can be developed that avoids changing the upgrade or its activation path.

Disagreement over impact and evidence

A prominent DeFi developer pointed to a list in the ethereum/repricing-impact repository that he said already covered 200,000 affected contracts. He also argued that methodological weaknesses meant the list could omit additional cases. That figure is therefore presented as part of a developer’s assessment, not as a confirmed total of contracts that will fail. The scope and completeness of the analysis remain points in the dispute.

The same developer said the effects could reach deployment and operation at several high-profile protocols, rather than being confined to obscure or rarely used code. His criticism focuses both on the proposed repricing and on how its impact has been assessed. The supplied account does not name the protocols or independently verify the claimed reach, so the warning underscores the need for case-by-case evidence rather than settling how extensive the risk is.

Another developer said his team had identified the same problems before Glamsterdam went live on the Sepolia testnet, and before a security firm later flagged them. That account raises questions about when relevant concerns were found and how they were incorporated into review. It does not, by itself, establish that the testnet exposed all possible failures or that the proposed change has already caused damage on a live network.

Supporters reconsider the case for speed

Opposition has come from developers and people involved in Ethereum’s broader technical community. The founder of Curve Finance warned that the upgrade could lead to an emergency hard fork reverting the change, while another DeFi developer called the proposal unreasonable. An Ethereum Foundation board member also objected to pushing a fork that could break assumptions previously treated as invariants. Their comments signal substantial concern, not a final decision by core developers.

The debate also prompted a public reversal from an influential Ethereum community member who had initially urged Glamsterdam’s activation as soon as possible. He had argued that Ethereum guarantees access to the network, rather than particular gas prices. Hours later he said the upgrade should not proceed on that fast timetable and acknowledged that his earlier position was wrong, describing the issue as more serious than generally understood.

In explaining the change of view, the advocate said the community had collectively fallen short on design, due diligence and public communication. He singled out gas introspection as a serious issue requiring immediate attention and much more visibility. Those comments shift the debate beyond the mechanics of repricing: developers are also being asked to show how risks were evaluated, how findings were shared, and whether affected projects had a meaningful chance to respond.

Upgrade timetable and unanswered questions

Glamsterdam’s current controversy follows an earlier delay. In October, core developers postponed a Glamsterdam test on the Hoodi testnet after security researchers flagged risks. Glamsterdam is one of two major Ethereum upgrades developers had planned for 2026. The earlier delay shows that review concerns have already influenced testing, but the supplied information does not say how the Hoodi findings relate to the current EIP-8037 objections or what changes followed.

Core developers now face pressure to publish more data before Glamsterdam reaches mainnet. The practical question is whether further testing and analysis can identify which contracts depend on the gas assumptions being changed, and what remedies are available where those contracts cannot be patched. The source gives no final timetable, revised proposal, or core-developer decision. It therefore remains unclear whether the upgrade will be delayed, modified, or advanced after additional review.

The dispute is unfolding alongside other Ethereum developments, though the source does not link them causally. Ethereum exchange-traded funds recorded their worst month for flows since launch, while co-founder Vitalik Buterin has described the subsequent Hegota upgrade as Ethereum’s last “normal” fork. These points add context to a busy upgrade period, but do not answer the technical questions around Glamsterdam. For now, the central uncertainty is whether its gas changes can proceed without disrupting existing contracts.

Source: BeInCrypto