Ethereum Delays Glamsterdam Testing Over Risk to Up to 15,000 Contracts
Ethereum developers have delayed public testing of the Glamsterdam upgrade over risks to as many as 15,000 smart contracts. Core proposals EIP-8037 and EIP-8038 alter storage and data retrieval fees, prompting security audits.
The Ethereum Glamsterdam upgrade could disrupt up to 15,000 smart contracts, Ethereum Foundation developer Marius van der Wijden told colleagues on Monday, according to CoinDesk’s November 17 account. Compatibility concerns have delayed public testing of changes to the network that supports ETH and its applications.
Core developers plan to revisit the proposals Thursday after Monday’s discussion ended without agreement. The Foundation says the Hoodi testnet rollout will remain on hold until the bugs are resolved.
Ethereum Glamsterdam Upgrade Review Expands Compatibility Concerns
What did the latest developer review identify?
Van der Wijden put the potentially affected population at up to 15,000 contracts within roughly 90 million deployed on Ethereum. He estimated that a few hundred thousand dollars could be at risk across those contracts.
Read More: Two Ethereum Proposals Aim to Protect 200,000 Contracts From Glamsterdam
The warning concerns programs already operating under Ethereum’s existing rules. Its significance is the possibility that a network upgrade could disrupt deployed software whose developers built around the current cost of executing particular operations.
Which Glamsterdam proposals are under scrutiny?
The discussion centers on EIP-8037 and EIP-8038, proposals that would change how Ethereum charges for storing and retrieving data. EIP-8037 would introduce a separate charge for creating permanent state, including deploying a contract or adding a storage entry.
That change reaches beyond the price developers pay for new deployments. Existing applications can call other contracts with a predetermined gas allowance, making their behavior sensitive to changes in the charges imposed during those calls.
Foundation Researchers and Auditors Examine ETH Application Risks
Who commissioned the compatibility testing?
The Ethereum Foundation hired outside security firms to stress test the proposed changes against existing applications. Its own research and outreach to software teams ran alongside those external reviews.
The work combined broad scanning with closer examinations of particular contract behaviors. Van der Wijden presented the broader estimate during Monday’s developer call, while the security firms supplied findings from their more focused investigations.
Which researchers contributed to the debate?
Tanguy Rocher of ChainSecurity presented the firm’s findings. Dedaub conducted a separate review focused on contracts with unusual gas usage, examining software whose execution patterns warranted additional attention under the proposed accounting rules.
Foundation researcher Ansgar Dietrichs, who helped write the proposals, argued for proceeding with the upgrade. He also acknowledged that core engineers needed to communicate more clearly with outside developers whose applications would encounter the new rules.
October’s Hoodi Delay Set Up the November Review
What did the postponed Hoodi rollout include?
The canceled testnet activation also included a planned increase in Hoodi’s gas limit to 200 million, according to Cryptonews coverage republished by Yahoo Finance. Developers postponed that milestone to investigate how the new gas accounting would interact with contracts already deployed on Ethereum mainnet.
The October concerns included how applications handle failed operations. Researchers identified scenarios in which a contract could have a different amount of gas remaining than its developers expected, potentially changing what happens after an error.
How did the investigation develop through November?
The Foundation subsequently directed developers’ attention to eight core technical assumptions. Most of the compatibility problems described in the latest review stem from two of those assumptions, making particular execution patterns a focus of the investigation.
By Monday’s discussion, the work encompassed the broad scan, external audits and direct outreach to application teams. Testing remained delayed while developers considered both the compatibility findings and the consequences of changing or removing the proposals.
Why Glamsterdam Could Change Unmodified Contract Behavior
How can new gas rules affect existing applications?
Some applications were written around predictable costs for specific operations. When those costs change, an operation that previously fit within an application’s execution budget can require more gas than the software allows.
Related: Vitalik Buterin Backs leanPCS to Speed Up Quantum-Safe Ethereum
The October investigation also highlighted assumptions about gas remaining after failed operations. An application may depend on that remaining allowance to run its error-handling logic; changing the accounting can therefore affect how it responds when another operation fails.
Why does immutable code remain exposed to protocol changes?
The developer discussion exposed a tension in Ethereum’s promise of immutable software. A deployed contract’s code can remain unchanged while the network rules governing its execution change beneath it.
For application teams, the relevant concern is whether their existing logic continues to behave as intended under the revised rules. For Ethereum’s engineers, the challenge is to improve the network while accounting for software that developers may have designed to remain permanently deployed.
Glamsterdam Gas Charges and Audit Findings in Numbers
How much would deployment and storage charges increase?
Under the described EIP-8037 proposal, deploying a contract would cost 183,600 gas, up from 32,000. That is roughly 5.7 times the current charge, illustrating the size of the adjustment for software that creates new contracts.
Creating a new storage slot would cost 97,920 gas, up from 20,000, or roughly 4.9 times the current charge. Both increases concern state creation, the activity that adds persistent information to Ethereum’s underlying database.
What did ChainSecurity and Dedaub find?
ChainSecurity presented 152 findings. About half overlapped with the Foundation’s internal research, putting their combined findings at roughly 200, according to the developer-call summary described in the November coverage.
Dedaub examined about 25,000 contracts with unusual gas usage and flagged 70 medium- and high-risk issues. Its review included 22 issues the Foundation had missed, adding specific cases for engineers and application teams to investigate.
How large was the estimated contract exposure?
Van der Wijden’s upper estimate represents about 0.017% of Ethereum’s roughly 90 million contracts. Even at that small share, the absolute number makes compatibility across existing software a substantial testing task.
His estimate of a few hundred thousand dollars potentially at risk places the concern in financial terms. The immediate engineering problem is determining which execution patterns fail under the proposed rules and how to address them before public testing proceeds.
Ethereum Developers Weigh Compatibility Against Upgrade Goals
Why are engineers proposing higher state-creation charges?
The fee changes aim to keep Ethereum’s underlying database from expanding too rapidly as future updates allow more activity in each block. Charging separately for permanent state creation is part of that effort to manage the consequences of increased network capacity.
The proposal therefore links an upgrade objective to a compatibility cost. Engineers want room for more activity while limiting database growth, but applications written around the existing charges may need changes to operate under the revised system.
Why did participants warn against dropping EIP-8037?
Some participants argued that abandoning EIP-8037 could obstruct developers’ ability to deploy larger contracts and weaken Glamsterdam’s security goals. Those arguments formed part of the case for retaining the proposal despite the problems identified during testing.
Dietrichs supported moving forward while calling for better communication with application developers. The resulting debate concerns how to preserve the intended improvements while dealing with the contracts whose assumptions conflict with the new accounting.
Thursday’s Glamsterdam Discussion Is the Next ETH Milestone
What will core developers reconsider Thursday?
Core developers plan to return to the proposals after Monday’s meeting ended without agreement. Their discussion follows both the external audit findings and the broader warning about potentially affected contracts.
The choice involves the proposed gas rules, their interaction with existing applications and the upgrade objectives participants want to preserve. Thursday’s planned discussion is the next decision point in that process, with Hoodi still waiting for compatibility fixes.
What stands between the review and a mainnet rollout?
The Foundation has tied resumption of Hoodi testing to resolution of the bugs. That leaves the public testnet stage dependent on the compatibility work now being undertaken by core engineers and application teams.
The latest developer discussion leaves Glamsterdam without a confirmed release date, making the resolution of testing problems the immediate milestone for ETH users following the upgrade.
?FAQ
01Which planned Hoodi activation date was canceled in October?
Developers canceled the activation scheduled for October 26. They used the postponement to investigate interactions between the proposed gas-accounting changes and existing mainnet contracts.
02When did the Ethereum Foundation warn developers about eight technical assumptions?
The Foundation issued that warning on November 6. Its guidance asked developers to review assumptions relevant to compatibility with the proposed changes.
03Why are contracts that forward a fixed gas allowance vulnerable to the proposed changes?
A contract may send another contract enough gas for an operation under the current charges. If the proposed rules make that operation more expensive, the fixed allowance may no longer cover it and the call could fail.
04What would EIP-8037 charge separately from ordinary execution gas?
EIP-8037 would separate the charge for creating permanent state from ordinary execution gas. The covered activities include deploying new contracts and adding permanent storage entries.
05Which contracts did Dedaub select for its compatibility review?
Dedaub targeted approximately 25,000 contracts displaying unusual gas usage. That selection concentrated its review on contracts with execution patterns relevant to the proposed changes.
06What patching progress did the Foundation report from its developer outreach?
The Foundation’s outreach identified three high-severity flaws and at least 25 medium-severity flaws. Most of the problems found through that outreach were already being patched.
07What other architectural changes are part of the Glamsterdam roadmap?
The October coverage also identified enshrined proposer-builder separation and block-level access lists among Glamsterdam’s proposed improvements. The gas-accounting compatibility review is taking place within that broader upgrade program.
This article is for information only and is not financial advice.



