What to Know

  • Ethereum’s planned Glamsterdam upgrade could disrupt as many as 15,000 smart contracts, based on an estimate shared by Ethereum Foundation developer Marius van der Wijden.
  • The potentially affected contracts represent a tiny fraction of roughly 90 million smart contracts on Ethereum.
  • Van der Wijden estimated that a few hundred thousand dollars could be at risk across the affected contracts.
  • The concerns center on EIP-8037 and EIP-8038, proposals that would change how Ethereum charges for storing and retrieving data.
  • Deploying a new contract would cost about 183,600 gas under the proposal, compared with 32,000 currently.
  • Creating a new data-storage slot would cost roughly 97,920 gas, compared with 20,000 currently.
  • Independent audits have found hundreds of potential compatibility issues, including medium- and high-risk findings.
  • Testing on the Hoodi public test network has been delayed since October, and Glamsterdam has no confirmed release date.
  • Core developers are set to revisit the proposals Thursday as the Ethereum Foundation says Hoodi will remain on hold until bugs are resolved.

Ethereum’s Glamsterdam Upgrade Runs Into Compatibility Concerns

Ethereum’s planned Glamsterdam upgrade is facing renewed scrutiny after developers flagged the possibility that as many as 15,000 smart contracts could be disrupted by proposed changes to the network’s fee mechanics. The estimate, shared during a developer call by Ethereum Foundation developer Marius van der Wijden, has sharpened a debate over how aggressively Ethereum should adjust its technical rules to manage long-term growth in the network’s underlying database.

The potentially affected programs are a small slice of Ethereum’s broader activity. The network hosts roughly 90 million smart contracts, which are self-executing pieces of software used for financial applications, digital asset transfers and automated on-chain operations. Still, the estimate is notable because it is far larger than the set of problems earlier reviews had identified. Van der Wijden also estimated that a few hundred thousand dollars could be at risk across the affected contracts, a relatively small amount compared with Ethereum’s wider ecosystem but still meaningful for users and developers tied to those applications.

Glamsterdam is intended to be a major technical step for Ethereum, but the latest discussion shows how difficult it can be to change core protocol rules on a network that already supports a large base of deployed software. Even if most applications remain unaffected, Ethereum’s design means that some contracts may be difficult or impossible to alter once deployed. That raises the stakes when changes to gas pricing alter assumptions that older programs may have embedded into their logic.

Why EIP-8037 and EIP-8038 Matter

The debate centers on two technical proposals known as EIP-8037 and EIP-8038. Together, the proposals would overhaul how Ethereum charges users and applications for storing and retrieving data. Every action on Ethereum requires gas, which functions as the unit used to measure computing work and determine transaction costs. While gas is a familiar concept for Ethereum users, the specific rules governing how gas is applied can have deep consequences for application design.

Under EIP-8037, Ethereum would separately charge for creating new permanent state. That could include deploying a contract or adding a new storage entry. Today, those costs are bundled into ordinary execution gas. The proposed structure would make certain state-expanding operations more expensive and more explicit. Deploying a new contract would cost about 183,600 gas, up from 32,000, while creating a new data-storage slot would cost roughly 97,920 gas, up from 20,000.

Ethereum engineers designed the fee increases to slow the growth of the network’s underlying database as future upgrades allow more activity to fit into each block. In broad terms, the concern is that permanent state places long-term demands on the network because nodes must keep track of more information over time. By making state creation more expensive, developers hope to discourage unnecessary database growth and preserve the network’s ability to scale securely.

That goal, however, collides with the reality that many existing applications were built around predictable costs or programmed to pass fixed gas allowances when calling other contracts. If a contract assumes that a certain operation will remain within a specific gas budget, a sudden increase can cause transactions to fail or applications to behave differently than expected. For users, that kind of failure may appear as a broken transaction. For developers, it can become a deeper compatibility problem if the affected contract cannot be upgraded easily.

Audits Find Hundreds of Potential Trouble Spots

To better understand which major applications might break under the new fee rules, the Ethereum Foundation hired outside security firms to stress test the proposed changes. Those reviews have added detail to the broader estimate of 15,000 potentially affected contracts and have revealed hundreds of specific compatibility concerns.

Tanguy Rocher of ChainSecurity reported 152 findings, with half overlapping with the Foundation’s internal research. Combined, that produced roughly 200 findings, based on a summary of Monday’s developer call posted on the Ethereum Magicians forum. A separate review by Dedaub examined about 25,000 contracts with unusual gas usage and flagged 70 medium- and high-risk issues. Of those, 22 had not been identified by the Foundation.

The findings suggest that the issue is not merely theoretical. While many smart contracts may continue operating normally, some appear to depend on cost assumptions that the proposed changes would alter. The Ethereum Foundation had previously warned developers about eight core technical assumptions on Nov. 6, and most of the newly identified problems stem from two of those assumptions. In its own outreach to software teams, the Foundation found three high-severity flaws and at least 25 medium-severity flaws, most of which are already being patched.

For Ethereum’s application ecosystem, the audit results present a mixed picture. On one hand, the number of potentially affected contracts is small relative to the full base of roughly 90 million smart contracts. On the other hand, the presence of high- and medium-severity issues shows that compatibility work is necessary before the proposals can move forward safely. Market participants and technical traders often view Ethereum upgrades through the lens of network utility, developer confidence and execution risk, making delays an important part of the broader market narrative.

The Immutability Debate Reaches the Forefront

The Glamsterdam discussion has also exposed a deeper tension in Ethereum’s design philosophy. Smart contracts are often described as immutable because their code can be deployed in a way that cannot be changed. That immutability is a core feature for many decentralized applications, since it allows users to verify rules and rely on them without trusting a central operator to make changes later.

Yet immutability does not mean the surrounding environment remains fixed forever. Ethereum’s protocol rules can change through upgrades, and those changes can affect how deployed contracts behave. A contract’s code may remain the same, but if the cost of a storage operation changes, the contract’s real-world execution may no longer match the assumptions under which it was written. Glamsterdam has turned that abstract issue into a concrete engineering challenge.

Ansgar Dietrichs, a Foundation researcher who helped write the proposals, argued during the developer call that the upgrade should move forward. He also acknowledged that core engineers needed to communicate more clearly with outside developers. That communication gap matters because application teams may need time to review contracts, patch upgradeable systems and warn users if certain interactions could be affected.

Other participants warned that scrapping EIP-8037 could create its own problems. Some developers said removing the proposal could block developers from deploying larger contracts and weaken the security goals of the upgrade. That leaves Ethereum’s core contributors weighing two kinds of risk: the compatibility risk of moving ahead with new fee rules and the structural risk of delaying or abandoning changes designed to control database growth.

Hoodi Test Network Delay Leaves Timeline Unclear

The immediate consequence is delay. Compatibility problems have held up testing since October, forcing engineers to postpone a planned rollout on Hoodi, a public test network. The Ethereum Foundation has said Hoodi will remain on hold until the bugs are resolved. Without that testing phase, Glamsterdam has no confirmed release date.

Core developers plan to revisit the proposal Thursday, and the next discussion may determine whether the current path remains intact, is modified, or is slowed further for additional compatibility work. Monday’s meeting ended without an agreement, underscoring that the technical and governance questions remain open.

For Ethereum users, the key issue is not simply whether Glamsterdam happens, but how the network balances innovation with reliability. Ethereum’s history has been shaped by regular upgrades aimed at improving scalability, efficiency and security. Each major change requires coordination across client teams, application developers, auditors, infrastructure providers and users. The larger the ecosystem becomes, the more complex that coordination gets.

Glamsterdam’s gas changes are intended to solve a long-term infrastructure problem, but the current debate shows that even carefully designed upgrades can carry unintended consequences for deployed applications. If developers can resolve the identified issues and improve communication with application teams, the upgrade may still proceed with stronger safeguards. If not, Ethereum may face a longer period of review before Glamsterdam reaches a public test network and, eventually, the main network.

What It Means for the Ethereum Ecosystem

For the broader crypto market, the Glamsterdam debate highlights Ethereum’s maturity as both a strength and a constraint. The network’s large base of applications gives it deep utility, but that same installed base makes protocol-level changes harder to implement. A young network can adjust rules quickly because fewer systems depend on them. Ethereum, by contrast, must consider a vast range of contracts, wallets, infrastructure tools and user expectations.

Some chart watchers may treat upgrade delays as a short-term sentiment factor, particularly when they raise questions about developer coordination. Longer term, however, the discussion is more about Ethereum’s ability to manage technical debt while continuing to scale. The database growth concerns targeted by EIP-8037 and EIP-8038 are not isolated issues; they are tied to how Ethereum can support more activity without increasing the burden on the infrastructure that keeps the network decentralized.

At the same time, the compatibility findings are a reminder that protocol changes can ripple into application logic in unexpected ways. Fixed gas allowances, predictable cost assumptions and older contract designs may all become pressure points when base rules change. That is why audits, public test networks and developer calls remain essential parts of Ethereum governance. They give the ecosystem a chance to find problems before users encounter them in production.

FXCOINZ will continue monitoring how core developers handle the Glamsterdam proposals, the Hoodi delay and the next round of compatibility discussions. For now, the upgrade remains a major Ethereum development to watch, with the outcome likely to shape expectations around future protocol changes and the practical limits of immutability in a constantly evolving blockchain environment.

Frequently Asked Questions (FAQs)

What is Ethereum’s Glamsterdam upgrade?

Glamsterdam is a planned Ethereum upgrade that includes proposed technical changes to how the network handles certain costs and operations. It has not received a confirmed release date because developers are still debating compatibility issues.

Why could Glamsterdam disrupt smart contracts?

The upgrade could alter gas costs for creating permanent state, such as deploying contracts or adding storage entries. Some existing smart contracts were built around older cost assumptions or fixed gas allowances, which may cause them to fail under the proposed rules.

How many Ethereum smart contracts could be affected?

Ethereum Foundation developer Marius van der Wijden estimated that as many as 15,000 smart contracts could be disrupted. That is a tiny fraction of the roughly 90 million smart contracts on Ethereum.

How much value could be at risk?

Van der Wijden estimated that a few hundred thousand dollars could be at risk across the potentially affected contracts. That amount is small relative to Ethereum’s broader ecosystem, but it remains important for users and developers connected to those contracts.

What are EIP-8037 and EIP-8038?

EIP-8037 and EIP-8038 are technical proposals that would change how Ethereum charges for storing and retrieving data. EIP-8037 would add separate charges for creating new permanent state, including contract deployment and new storage entries.

How would gas costs change under the proposal?

Deploying a new contract would cost about 183,600 gas instead of 32,000. Creating a new data-storage slot would cost roughly 97,920 gas instead of 20,000.

What did independent audits find?

Audits found hundreds of potential compatibility issues. ChainSecurity reported 152 findings, while Dedaub reviewed about 25,000 contracts with unusual gas usage and flagged 70 medium- and high-risk issues, including 22 that the Foundation had missed.

Why is the Hoodi test network delayed?

Testing on Hoodi has been delayed because developers want the compatibility bugs resolved before moving forward. The Ethereum Foundation has said Hoodi will remain on hold until those issues are addressed.

When will Glamsterdam launch?

Glamsterdam has no confirmed release date. Core developers are set to revisit the proposals Thursday, and the timeline will depend on whether the compatibility concerns can be resolved.