Loading live prices…
Ethereum

Ethereum Glamsterdam Upgrade Risks Breaking 15,000 Smart Contracts as Tests Stall

Ethereum’s next major upgrade has run into its most serious obstacle yet. The Glamsterdam upgrade, the network’s next planned hard fork, could disrupt as many as 15,000 smart contracts and put a few hundred thousand dollars at risk, according to Ethereum Foundation developer Marius van der Wijden, who raised the figure on a developer call on Monday. The number is small next to the roughly 90 million smart contracts deployed on Ethereum, but it is far larger than earlier reviews had suggested, and it has forced core developers to pause testing and rethink parts of the plan. The problem sits in two proposals, EIP-8037 and EIP-8038, which change how the network charges users and applications for storing and reading data. With no agreement reached on Monday and no release date on the calendar, Glamsterdam’s timetable is now genuinely uncertain, and the debate inside the developer community has become a test of how Ethereum balances ambitious technical change against the safety of the applications already running on it.

Advertisement

Why the Ethereum Glamsterdam Upgrade Puts 15,000 Contracts at Risk

The headline figure came from Marius van der Wijden, a developer at the Ethereum Foundation, speaking on the regular developer call on Monday. He told fellow developers that Glamsterdam could disrupt as many as 15,000 smart contracts and put a few hundred thousand dollars at risk. The scale of the exposure surprised even people close to the process, because earlier reviews of the upgrade’s impact had identified far fewer affected programs. Fifteen thousand contracts still represent a tiny fraction of the roughly 90 million smart contracts that exist on Ethereum, yet the absolute number matters more than the percentage. Each of those contracts may hold user funds, serve as a building block for other applications, or sit at the centre of a service that ordinary people rely on without ever knowing a smart contract is involved.

The reason so many programs are exposed is that a large share of them were written on the assumption that certain costs on Ethereum would stay roughly the same. Many existing applications were built to pass a fixed gas allowance when calling other contracts, a common pattern in which one program hands another a strict budget for the work it is asked to do. Others were designed around the predictable cost of creating new storage, a routine operation for applications that keep records on the network. Under the new rules proposed for Glamsterdam, those assumptions no longer hold. A call that once cost a known amount may now cost far more, and a contract that once completed its work inside a fixed budget may run out of gas halfway through. When that happens, the transaction fails, and depending on how the application was written, the failure can cascade into other parts of the system.

EIP-8037 and EIP-8038: The Gas Changes at the Centre of the Dispute

At the heart of the dispute are two Ethereum Improvement Proposals, EIP-8037 and EIP-8038, which together overhaul how Ethereum charges users and applications to store and retrieve data. The proposals are part of a long-running effort to control the growth of the network’s database, the ever-expanding record of accounts, balances and contract data that every node on the network must store. As that database grows, running a node becomes more expensive and more demanding, which over time threatens the decentralisation that Ethereum depends on. The new pricing is meant to slow that growth by making the most expensive operations cost more, discouraging wasteful storage and pushing developers toward leaner designs.

Advertisement

The scale of the price changes at the centre of the EIP-8037 EIP-8038 gas costs debate is what makes them so disruptive. Under EIP-8037, deploying a new contract would cost around 183,600 gas, up from 32,000 under the current rules, an increase of nearly six times. Creating a new data-storage slot would cost around 97,920 gas, up from 20,000, a rise of close to five times. For a new application built with these prices in mind, the higher costs are an inconvenience that can be planned around. For an existing application that hard-coded the old prices into its logic, they can be fatal. A contract that reserves exactly 32,000 gas for a deployment step, or that passes a fixed allowance to another contract expecting it to be enough, will simply fail when the real cost turns out to be several times higher.

What the Audits Found: 200 Issues and Counting

The 15,000 figure did not emerge from guesswork. It is the product of an unusually thorough review process that combined the Foundation’s own research with independent audits. ChainSecurity, a specialist auditing firm, reported 152 findings in its review of the proposals, and its researcher Tanguy Rocher noted that about half of those overlapped with the Foundation’s internal research, bringing the combined total to around 200 issues. That overlap is itself informative: it suggests that two separate teams, working independently, kept arriving at the same problem areas, which is a sign that the risks are real rather than the product of one team’s caution.

A second audit added a different kind of evidence. Dedaub, another security firm, examined around 25,000 contracts that showed unusual gas usage patterns, the kind of pattern that suggests a program is doing something the new rules might punish. From that group it flagged 70 medium- and high-risk issues, including 22 that the Foundation’s own researchers had missed. The Foundation’s outreach to developers produced further findings: three high-severity flaws and at least 25 medium-severity ones, most of which are already being patched. Taken together, the three efforts paint a picture of a problem that is wider than first thought, but also one that is being actively mapped and, in many cases, fixed before the upgrade ships.

Why the Ethereum Hoodi Testnet Delay Matters

The dispute came to a head on Monday, when the developer meeting ended without agreement on how to proceed. That lack of consensus is significant in itself, because Ethereum’s upgrade process depends on broad agreement among core developers before a change moves forward. But the more concrete consequence is what has happened to testing. Compatibility problems have delayed testing since October, and the delays have now postponed a planned rollout on Hoodi, a public test network where upgrades are trialled under realistic conditions before they reach the main network. Hoodi remains on hold until the bugs are resolved, which means the most important stage of pre-launch testing has not yet begun.

Advertisement

The Ethereum Hoodi testnet delay matters because test networks are where the consequences of an upgrade are discovered in practice rather than in theory. Developers deploy their applications to Hoodi, run them against the new rules, and see what breaks. Without that stage, the audit findings remain estimates, and the patching work cannot be properly validated. A testnet delay also compresses everything that comes after it: if testing starts late, the mainnet launch must either slip or proceed with less evidence than the developers would like. For an upgrade that touches the economics of every contract on the network, that is not a comfortable choice, and it is one of the reasons the tone of Monday’s meeting was so cautious.

What Happens Next: The November 19 Meeting and the Road Ahead

Core developers plan to revisit the proposal on Thursday, November 19, and that meeting will be the next real test of whether Glamsterdam can move forward in its current form. The options on the table are stark. One is to press ahead, accepting that some contracts will break and relying on the patching effort to limit the damage. Another is to modify or drop EIP-8037, the more disruptive of the two proposals, and accept a slower fix for the state-growth problem. A third is to delay the upgrade while the compatibility work continues, which would protect existing applications but leave the underlying problem unaddressed for longer.

The arguments on each side were already aired on Monday. Ansgar Dietrichs, a Foundation researcher who helped write the proposals, argued that the upgrade should move forward, a position that reflects the view that state growth is a structural risk that cannot be postponed indefinitely. Others warned that scrapping EIP-8037 could block larger contract deployments and weaken the security goals the upgrade is meant to achieve, a reminder that the proposal is not an arbitrary price rise but part of a deliberate design. What neither side disputes is that the decision cannot be rushed. Glamsterdam has no confirmed release date, and the absence of a date is itself a signal: the developers are not willing to commit to a launch while the compatibility picture remains unresolved.

Frequently asked questions

What is the Ethereum Glamsterdam upgrade?
Glamsterdam is the next planned hard fork of the Ethereum network. It includes EIP-8037 and EIP-8038, two proposals that change how the network charges for storing and retrieving data, with the aim of slowing the growth of Ethereum’s database.

Advertisement

How many smart contracts could the upgrade break?
As many as 15,000 smart contracts could be disrupted, according to Ethereum Foundation developer Marius van der Wijden. That is a small share of the roughly 90 million contracts on Ethereum, but far more than earlier reviews had found, and a few hundred thousand dollars could be at risk.

Why would the new gas prices break existing contracts?
Many contracts were written assuming the current costs, or they pass a fixed gas allowance when calling other contracts. Under EIP-8037, deploying a contract would cost about 183,600 gas instead of 32,000, and a new storage slot would cost about 97,920 gas instead of 20,000, so calls built around the old prices can run out of gas and fail.

When will Glamsterdam launch?
There is no confirmed release date. Testing on the Hoodi test network has been postponed while compatibility problems are resolved, and core developers plan to revisit the proposal on Thursday, November 19.

Source: CoinDesk.

Advertisement

Related reading on MM Crypto Analysis Web

More in Ethereum on MM Crypto Analysis Web.

Advertisement
Advertisement

MM Crypto Team

MM Crypto Team covers crypto news, prices and market analysis.

One thought on “Ethereum Glamsterdam Upgrade Risks Breaking 15,000 Smart Contracts as Tests Stall”

Leave a Reply

Your email address will not be published. Required fields are marked *

Advertisement
Advertisement
Advertisement