Skip to content
Coin News Media
November 20, 2026
Coin News Media
ETH

Ethereum Delays Glamsterdam Testing Over Risk to Up to 15,000 Contracts

Ethereum has postponed testing for the Glamsterdam upgrade and the Hoodi testnet rollout due to compatibility issues that could impact up to 15,000 smart contracts and alter gas accounting methods.

Ethereum Delays Glamsterdam Testing Over Risk to Up to 15,000 Contracts

Public testing for the Ethereum Glamsterdam upgrade has been postponed due to compatibility issues that could impact up to 15,000 smart contracts, Ethereum Foundation developer Marius van der Wijden informed his colleagues on Monday, according to a report by CoinDesk on November 17. The network supports ETH and its various applications.

Following a Monday discussion that concluded without a consensus, core developers intend to reexamine the proposals on Thursday. The Ethereum Foundation stated that the Hoodi testnet rollout will remain paused until these bugs are successfully addressed.

Ethereum Glamsterdam Upgrade Review Expands Compatibility Concerns

What did the latest developer review identify?

Van der Wijden noted that up to 15,000 contracts out of roughly 90 million deployed on Ethereum could be affected. He calculated that a few hundred thousand dollars might be at risk across these specific contracts.

Read More: Two Ethereum Proposals Aim to Protect 200,000 Contracts From Glamsterdam

This warning affects programs already running under current Ethereum guidelines. The core issue is that a network upgrade could disrupt deployed software whose creators built their systems around existing execution costs for particular operations.

Which Glamsterdam proposals are under scrutiny?

The conversation focuses on EIP-8037 and EIP-8038, which propose altering how Ethereum bills users for data storage and retrieval. Specifically, EIP-8037 aims to introduce a distinct charge for generating permanent state, such as deploying a contract or adding a storage entry.

This adjustment reaches further than just the costs for new deployments. Because existing applications often call other contracts using a predetermined gas allowance, their behavior becomes sensitive to price fluctuations during those calls.

Foundation Researchers and Auditors Examine ETH Application Risks

Who commissioned the compatibility testing?

To stress-test the proposed modifications against current applications, the Ethereum Foundation enlisted independent security firms. These external reviews were conducted alongside the Foundation’s internal research and direct outreach to software teams.

The process merged wide-ranging scans with targeted evaluations of specific contract functionalities. Van der Wijden shared the broader estimate during Monday’s developer call, while the external security companies provided insights from their specialized investigations.

Which researchers contributed to the debate?

Tanguy Rocher shared ChainSecurity’s findings on behalf of the firm. Meanwhile, Dedaub performed a separate analysis targeting contracts with unconventional gas usage, evaluating software whose execution patterns required closer inspection under the suggested accounting regulations.

Foundation researcher Ansgar Dietrichs, a co-author of the proposals, advocated for moving forward with the upgrade. At the same time, he recognized that core engineers need to improve communication with external developers whose software will interact with the updated rules.

October’s Hoodi Delay Set Up the November Review

What did the postponed Hoodi rollout include?

As reported by Cryptonews and republished by Yahoo Finance, the canceled testnet activation also featured a planned lift in Hoodi’s gas limit to 200 million. Developers delayed this milestone to study how the new gas accounting methods would impact contracts already active on the Ethereum mainnet.

Concerns in October involved how applications manage failed operations. Researchers flagged instances where a contract might end up with a different amount of remaining gas than expected by its creators, potentially altering post-error behavior.

How did the investigation develop through November?

The Foundation subsequently directed developers’ attention toward eight core technical assumptions. Most compatibility issues highlighted in the recent review trace back to two of these assumptions, drawing heightened focus to specific execution behaviors.

By the time of Monday’s meeting, the initiative included comprehensive scans, external audits, and direct communication with application teams. Testing stays on hold as developers weigh the compatibility results alongside the implications of modifying or discarding the proposals.

Why Glamsterdam Could Change Unmodified Contract Behavior

How can new gas rules affect existing applications?

Certain applications were built expecting predictable costs for specific operations. When those costs shift, an operation that once fit inside an application’s execution budget may demand more gas than the software allows.

Related: Vitalik Buterin Backs leanPCS to Speed Up Quantum-Safe Ethereum

The October investigation also drew attention to assumptions surrounding leftover gas following failed transactions. Because an application might rely on that leftover allowance to execute error-handling protocols, changing the accounting logic can alter how the software reacts to failures.

Why does immutable code remain exposed to protocol changes?

The developer dialogue underscored a fundamental tension in Ethereum’s commitment to immutable software. While a deployed contract’s code stays identical, the underlying network rules governing its execution can shift.

For application teams, the main worry is whether their existing logic functions as intended under revised parameters. For Ethereum engineers, the objective is to upgrade the network while accounting for software that may have been designed to operate indefinitely without modification.

Glamsterdam Gas Charges and Audit Findings in Numbers

How much would deployment and storage charges increase?

Under EIP-8037, deploying a contract would cost 183,600 gas, rising from the previous 32,000. This represents roughly a 5.7-fold increase for software that generates new contracts.

Similarly, creating a new storage slot would cost 97,920 gas, up from 20,000—about 4.9 times the current rate. Both increases target state creation, the process that adds persistent data to Ethereum’s underlying database.

What did ChainSecurity and Dedaub find?

ChainSecurity reported 152 findings. Roughly half overlapped with the Foundation’s internal research, bringing their combined total to approximately 200 findings according to the developer-call summary outlined in November updates.

Dedaub analyzed about 25,000 contracts exhibiting unusual gas usage and identified 70 medium- and high-risk issues. This review included 22 issues previously missed by the Foundation, supplying specific edge cases for engineers and software teams to examine.

How large was the estimated contract exposure?

Van der Wijden’s higher-end estimate accounts for roughly 0.017% of Ethereum’s estimated 90 million contracts. Even at this minor proportion, the absolute volume makes ensuring cross-software compatibility a major testing undertaking.

His projection of a few hundred thousand dollars potentially at risk frames the issue financially. The immediate engineering hurdle is identifying which execution patterns break under the proposed framework and resolving them before public testing moves forward.

Ethereum Developers Weigh Compatibility Against Upgrade Goals

Why are engineers proposing higher state-creation charges?

Fee adjustments are designed to prevent Ethereum’s underlying database from expanding too quickly as upcoming updates accommodate higher block activity. Charging separately for permanent state generation supports broader efforts to manage the consequences of elevated network capacity.

Consequently, the proposal links an upgrade goal with a compatibility cost. Engineers want to create room for higher network activity while limiting database growth, but applications tailored to legacy fees may need updates to function under the updated system.

Why did participants warn against dropping EIP-8037?

Certain participants argued that abandoning EIP-8037 could hinder developers from deploying larger contracts and undermine Glamsterdam’s security objectives. These points formed the core argument for retaining the proposal despite issues uncovered during testing.

Dietrichs favored moving forward while emphasizing the need for improved communication with application developers. The ongoing debate centers on preserving intended network enhancements while accommodating contracts whose operational assumptions conflict with the new accounting methods.

Thursday’s Glamsterdam Discussion Is the Next ETH Milestone

What will core developers reconsider Thursday?

Core developers plan to revisit the proposals after Monday’s meeting wrapped up without a consensus. This upcoming conversation follows both external audit results and broader warnings regarding potentially impacted contracts.

The decision involves evaluating proposed gas rules, their impact on existing applications, and the upgrade objectives stakeholders wish to maintain. Thursday’s scheduled debate marks the next major decision point, with Hoodi remaining paused pending compatibility fixes.

What stands between the review and a mainnet rollout?

The Foundation has explicitly tied the revival of Hoodi testing to the successful resolution of these bugs. As a result, the public testnet phase relies entirely on ongoing compatibility efforts by core engineers and application teams.

Because the latest developer discussions left Glamsterdam without an established release date, resolving these testing challenges remains the critical milestone for ETH users tracking the upgrade.

FAQ

Which planned Hoodi activation date was canceled in October?

Developers called off the activation planned for October 26, using the postponement to study interactions between proposed gas-accounting adjustments and current mainnet contracts.

When did the Ethereum Foundation warn developers about eight technical assumptions?

The Foundation released this warning on November 6, urging developers to review assumptions tied to compatibility with the proposed alterations.

Why are contracts that forward a fixed gas allowance vulnerable to the proposed changes?

A contract might send another contract sufficient gas for an operation under existing rates. If the new rules make that specific operation costlier, the static allowance may fall short, causing the transaction call to fail.

What would EIP-8037 charge separately from ordinary execution gas?

EIP-8037 would separate fees for creating permanent state from standard execution gas, covering actions such as deploying new contracts and adding permanent storage entries.

Which contracts did Dedaub select for its compatibility review?

Dedaub focused on roughly 25,000 contracts demonstrating unusual gas usage, concentrating its analysis on execution patterns pertinent to the proposed updates.

What patching progress did the Foundation report from its developer outreach?

The Foundation’s outreach uncovered three high-severity flaws and at least 25 medium-severity flaws, most of which were already in the process of being patched.

What other architectural changes are part of the Glamsterdam roadmap?

October coverage also noted enshrined proposer-builder separation and block-level access lists among proposed Glamsterdam enhancements. The gas-accounting compatibility review occurs within this wider upgrade framework.

This article is for information only and is not financial advice.

Anastasia Viktorova

Web3 PR Specialist | KOL | Blockchain Advocate | Digital Strategy Expert based in Moscow, Russia. Focused on Web3 communications, blockchain, digital strategy, and community growth.

More from this author

Related stories

Comments 0 responses

Join the discussion

Comments are moderated and appear after review.