Ethereum’s next major software upgrade, codenamed “Glamsterdam,” could break as many as 15,000 automated programs on the network, a developer at the Ethereum Foundation revealed. The disclosure, made during a developer call on Monday, November 16, 2026, has already delayed testing and sparked debate among the blockchain’s core engineers.
The developer, Marius van der Wijden, estimated that while the number of affected smart contracts is a tiny fraction of the 90 million deployed on Ethereum, they could put a few hundred thousand dollars at risk. The potential for disruption has stalled progress on the upgrade, which currently has no confirmed release date.
Proposed fee changes at the heart of the Glamsterdam upgrade
The controversy centers on two technical proposals, known as EIP-8037 and EIP-8038. These changes are designed to overhaul how Ethereum charges for data storage and retrieval, a mechanism known as “gas.” The goal is to slow the rapid growth of the network’s database, a problem often called “state bloat.”
Under the proposed EIP-8037, the cost for certain operations would increase dramatically. For example, deploying a new smart contract would jump from 32,000 gas to approximately 183,600 gas. Creating a new data-storage slot within a contract would rise from 20,000 gas to nearly 98,000 gas.
While intended to secure the network’s future scalability, these adjustments threaten to break existing applications. Many developers wrote their smart contracts assuming that gas costs would remain relatively stable and predictable. Some applications even use fixed gas allowances when interacting with other contracts, a practice that would fail under the new fee structure.
This situation highlights a fundamental tension in blockchain development: the need to evolve the protocol versus the promise of immutability. Contracts deployed with unchangeable code can still have their behavior unexpectedly altered by underlying rule changes, affecting the entire altcoin market cap evolution and user trust.
Audits uncover hundreds of compatibility problems
To gauge the potential damage, the Ethereum Foundation hired external security firms to audit the proposed changes. While broad network scans identified the 15,000 potentially vulnerable contracts, deeper analysis by auditors has pinpointed hundreds of specific, high-risk trouble spots across the ecosystem.
Tanguy Rocher from the security firm ChainSecurity reported 152 distinct findings. When combined with the Foundation’s own internal research, the total number of identified issues rose to roughly 200. Understanding such technical shifts is crucial for participants monitoring altcoin market dynamics. This detailed review gives a clearer picture of how widespread the disruptions could be for certain types of applications.
A separate audit by another firm, Dedaub, took a different approach. It examined 25,000 contracts known for unusual gas consumption patterns. This targeted analysis flagged 70 medium- and high-risk issues, including 22 critical problems that the Foundation’s initial scans had missed completely.
Most of the compatibility issues stem from a handful of core assumptions that developers have historically relied on. The Foundation published a list of eight such assumptions on November 6, warning software teams to review their code. In its own outreach, the Foundation found three high-severity flaws and at least 25 medium-severity ones, many of which are now being patched by their respective teams.
A growing rift among developers
The audit findings have exposed a deeper disagreement among Ethereum’s core developers about how to proceed. During the November 16 call, Ansgar Dietrichs, an Ethereum Foundation researcher who co-authored the proposals, argued that the upgrade should move forward despite the risks. He did, however, concede that core engineers needed to improve their communication with the broader developer community.
But other participants on the call expressed serious reservations. They warned that moving forward too quickly could undermine the trust developers place in the platform. The debate touches on the philosophical promise of Ethereum, where contracts are meant to be immutable and their behavior predictable over time.
Some developers also noted a counter-risk: scrapping EIP-8037 entirely could cause its own problems. It’s not just about fees. Abandoning the proposal could block developers from deploying larger contracts and weaken the upgrade’s security goals, according to one developer.
Glamsterdam timeline uncertain as testing remains on hold
The practical consequence of this debate is delay. Compatibility issues have already forced engineers to postpone the upgrade’s planned rollout on Hoodi, a public test network used for large-scale stress testing. The testnet deployment has been on hold since October, and Monday’s meeting ended without a resolution.
Core developers plan to revisit the contentious proposals during their next meeting on Thursday. Until the bugs and compatibility issues are resolved, the Hoodi testnet activation will remain paused. This leaves the mainnet launch of the Glamsterdam upgrade without a clear timeline.
This uncertainty comes at a sensitive time for the crypto market. Broader sentiment has been shaky, with questions about general crypto market trends. A contentious or delayed upgrade to Ethereum, the second-largest asset, could add to investor anxiety, even if the direct financial risk from broken contracts is relatively small.
For now, the future of Glamsterdam rests on whether developers can find a compromise. They must balance the long-term health of the network against the immediate stability of the applications and assets that rely on it. The path forward will likely involve more audits, intense debate, and a cautious approach to implementation.
