Ethereum's Glamsterdam upgrade risks breaking up to 15,000 automated apps
- Published
- Updated
Ethereum developers reviewed a compatibility estimate for the proposed Glamsterdam upgrade, with an upper figure of up to 15,000 deployed contracts. The estimate was discussed on a November 16, 2026 core developer call and was framed as a review figure rather than evidence of failed mainnet contracts.
Key claims & sources
What it means
Ethereum’s Glamsterdam work is part of the normal process of changing the network’s rules while preserving what already runs on it. A core developer call on November 16, 2026 put a number on the compatibility review, which shows the upgrade is being checked against deployed contracts before it moves further. For builders and operators on Ethereum, that means protocol changes are being measured not only for new features but also for whether existing automated applications still fit the new rules.
If an upgrade touches deployed contracts, teams that maintain on-chain software may need to review code, redeploy systems, or adjust how they interact with Ethereum after the change lands. The practical issue is not just technical cleanup; it is whether an existing contract keeps working under the network’s new behavior. That puts pressure on developers to track upstream protocol work closely instead of assuming old deployments will remain untouched. (per coindesk.com)
Ethereum keeps trying to improve the base layer while leaving a huge installed base of smart contracts in place, and that creates a built-in tension between forward progress and backward compatibility. A large compatibility estimate highlights how much risk can sit in the gap between a network upgrade and the applications already built on top of it. The trade-off is visible here: a stronger or cleaner protocol can still impose real migration work on the people who built around the earlier rules.
The open question is which of the contracts in the estimate would actually need changes once Glamsterdam’s final specification is set. The call description leaves unresolved how many deployments would be affected in practice, and the figure itself was presented as an upper estimate rather than a failure tally. What settles it is the final upgrade design and the next round of compatibility checks against live Ethereum deployments.
Market reaction i
Ethereum fell 2.6% in the 4 hours after the first headline, after rising 1.0% in the 2 hours before.
35 prices, one every 30 minutes
Coverage timeline
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Has this happened before?
| When | What happened | Figure |
|---|---|---|
| 5 days ago | Ethereum researchers drop faster blocks to race toward quantum defenses in 2027 event | 1 actors in common · 2 news media |
| 10 days ago | Bitcoin Developer Proposes a Quantum Trap for Hackers event | 1 actors in common · 2 news media |
| 11 days ago | EIP-8037/EIP-8038 Glamsterdam event | 1 actors in common · 11 news media |
| 11 days ago | BNB Chain, Base respond to Reth security bug affecting EVM networks event | 1 actors in common · 4 news media |
| 14 days ago | Ethereum dev targets 2028 for quantum resistance, a year early event | 1 actors in common · 6 news media |