Logo Daily Crypto Briefs
Open menu

Ethereum Glamsterdam Could Disrupt 15,000 Contracts

4 min read
Large official black Ethereum diamond on an ivory limestone sign beside an unbranded grayscale circuit breaker, against violet and orange panels.

TL;DR

  • Marius van der Wijden put the upper estimate of potentially affected contracts at 10,000–15,000 during Monday's developer call.
  • New audits identify compatibility problems; these counts do not measure hacked wallets or realized losses.
  • Developers will discuss specifications and next steps on November 19. No mainnet activation date is confirmed.

CASABLANCA, Nov. 17, 2026

Ethereum’s proposed Glamsterdam upgrade could disrupt as many as 15,000 smart contracts, an Ethereum Foundation developer estimated Monday, as fresh audit findings put application compatibility before a November 19 review of the network’s scaling plans.

The new assessment gives developers a broader picture of potential disruption following the October postponement of Hoodi testing. The immediate question is whether Ethereum should revise its proposed gas rules before advancing the upgrade.

Ether closed Monday’s UTC session at $1,819.02 on Coinbase Exchange, down 0.85% from Sunday and 24.8% from October 16. About 189,503 ETH traded in that venue’s dollar pair Monday. Those figures describe market conditions without establishing a price response to the developer discussion.

Ethereum

ETH
Oct. 16 to Nov. 16, 2026 UTC
$1,819
-24.8%
Oct 16 - Nov 16 | High $2,472 • Low $1,819

Sampled completed UTC daily closes from Coinbase Exchange.

Glamsterdam audits widen the contract review

Marius van der Wijden put the highest estimate at roughly 10,000–15,000 potentially affected contracts out of about 90 million deployed on Ethereum during the November 16 testing call. He described value in contracts whose teams had not yet committed to upgrading as being on the order of a few hundred thousand dollars, while explicitly cautioning that he lacked reliable figures.

That estimate describes possible exposure, not money already lost. As of November 17 at 22:00 UTC, the reviewed primary disclosures and targeted searches did not establish observed thefts, victim-wallet counts, stolen-fund transactions or a realized loss total attributable to the proposed changes. Ethlabs said November 10 that the issues it described depended on possible deployment of Glamsterdam’s current specifications.

The meeting’s published summary reports 152 ChainSecurity findings, with 76 overlapping the Foundation’s internal work. These findings concern classes of contracts, so they should not be added to the broader estimate as separate victims.

Dedaub’s presentation provides another reason to keep categories separate. At roughly 40 minutes into the recording, its representative reported 12 high and 70 medium findings in one analysis, confirmed through transaction replays. These audit results describe different search methods and overlapping contract populations, rather than a single deduplicated total.

EIP-8037 changes gas failure behavior

EIP-8037 changes how Ethereum charges for creating persistent data, while EIP-8038 updates costs for accessing existing data. Gas measures the work a transaction asks the network to perform.

The repricing supports the broader plan to raise block capacity toward 200 million gas. Applications built around fixed allowances may need more gas for the same operation under the proposed rules.

ChainSecurity’s analysis identifies a separate concern: changes in gas accounting can let a contract complete its failure handler after an inner operation runs out of gas. A transaction may finish while the payment or message it was meant to carry out fails.

Simulations published by Juicebox developer Jango illustrate the distinction. Tests against deployed Juicebox V6 code on Glamsterdam Sepolia showed paths where a payout completed but a split payment was skipped, or a cash-out completed with its fee forgiven. The repository records simulated comparisons with mainnet, rather than reports of successful thefts.

Changing a wallet’s gas allowance may address some compatibility problems. It cannot by itself rewrite a constant embedded in an immutable contract or guarantee that a failed internal operation remains recoverable.

November 19 review leaves Hoodi unresolved

The Ethereum Foundation’s updated timetable schedules discussion of findings and possible next steps for November 19, with no decision pre-committed. Hoodi remains on hold pending resolution, and no mainnet activation date is confirmed.

The Foundation’s gas-invariants repository gives auditors and app teams examples of assumptions that change. It also flags off-chain systems, including services that interpret transaction receipts. Reviewing contract code alone may therefore miss part of an application’s exposure.

Alternative.me’s Crypto Fear & Greed Index stood at 12 on Tuesday UTC, up from 10 Monday and still in extreme fear.

Fear & Greed Index

Nov. 17, 2026
12 Extreme Fear

The next concrete milestones are a decision on specifications, a revised Hoodi schedule and confirmation that affected applications have working mitigations. Monday’s findings sharpened the compatibility question; they did not resolve the final scope or timing of the upgrade.

Stay up to date

Get the latest crypto insights delivered to your inbox

Fact-checked by: Daily Crypto Briefs Fact-Check Desk

Frequently Asked Questions

Will Glamsterdam break 15,000 Ethereum contracts?

That is the upper end of a developer estimate of potentially affected contracts, not a confirmed outcome. Specifications and mitigations remain under review.

Has the Glamsterdam issue caused stolen funds?

The reviewed disclosures did not establish thefts or realized losses as of November 17 at 22:00 UTC. The concerns involve proposed mainnet rules and test simulations.

When will Ethereum developers review Glamsterdam again?

The Ethereum Foundation's timetable lists November 19 for the execution-layer developer discussion of findings and possible next steps, with no decision pre-committed.

What should Ethereum app teams check?

Teams should test fixed gas budgets, failure handling, relayers and other assumptions against the published gas invariants. Some fixes may require changing settings, upgrading contracts or redeploying them.