Ethereum's planned Glamsterdam upgrade could break as many as 15,000 automated apps, according to independent audits that found hundreds of separate compatibility problems tied to the changes. Core developers are set to reconsider the upgrade on Thursday.
What the audits turned up
The audits, carried out independently of the core development process, didn't flag one or two edge cases. They surfaced hundreds of distinct compatibility issues across the software that runs on top of Ethereum. The upper estimate of affected apps runs to 15,000.
That's a wide blast radius for what's still a planned network change. The word "audits" matters here: these aren't developer hunches or forum speculation. They're structured reviews that put specific problems on paper, which is presumably why the findings reached the level of a full reconsideration.
The apps in the crosshairs
The affected software is described as automated apps — programs that execute on their own logic rather than waiting on a human to push a button. When a network upgrade changes the rules those programs run under, the fallout isn't cosmetic. Contracts that assumed one behavior can fail outright under another.
The exact split between "will break" and "might break" isn't spelled out in the auditors' findings, and the 15,000 figure is an upper bound. Still, even a fraction of that number is a lot of software to leave sitting on an upgrade that hasn't shipped yet.
Thursday's decision
Core developers will take the findings up on Thursday. What they do with the audits is the open question. They could push the upgrade through as planned, adjust the changes to address the compatibility problems, or delay. None of those options is free.
Pushing ahead risks breaking live apps on day one. Adjusting the changes means more development cycles on a network upgrade that already carries a lot of expectations. A delay is the simplest to announce and the least satisfying to everyone who's been building toward Glamsterdam on the current timeline.
A familiar friction point
Network upgrades always strain the software built on top of them. The difference this time is that the strain is documented before the change goes live, in hundreds of separate findings, rather than discovered after users start reporting failures.
That gives developers something they rarely get: a warning shot. Whether they act on it is what Thursday's meeting is for.
The core developers' decision is expected at that session. Until then, the apps in question — and the teams running them — are working off an upper bound of 15,000 and a list of audit findings that hasn't been publicly resolved.




