For developers maintaining deployed Ethereum contracts, the unresolved question is whether the planned Glamsterdam upgrade could affect how their code behaves. In a report published on November 17, 2026, Foresight News, citing CoinDesk, said Ethereum Foundation developer Marius van der Wijden told a November 16 developer call that as many as 15,000 on-chain automation programs might be affected. Funds associated with potentially affected contracts were estimated in the hundreds of thousands of dollars. The estimated number of programs was far larger than earlier reviews had identified.
What the reviews found
ChainSecurity’s Tanguy Rocher reported 152 findings, about half of which overlapped with the foundation’s internal research. Together, the reviews identified roughly 200 potential issues. In a separate review of about 25,000 contracts with unusual gas usage, Dedaub flagged 70 medium- or high-risk issues, including 22 the foundation had previously missed. Most of the issues stemmed from two of the eight core technical assumptions about which the foundation had warned developers on November 6.
The foundation also identified three high-severity and at least 25 medium-severity defects through its communications with outside developers. Most were being fixed at the time of the report.
Deployment remains undecided
Researchers and developers did not reach agreement on the November 16 call. Ansgar Dietrichs, a researcher involved in writing the proposal, argued that the upgrade should proceed while acknowledging that core engineers needed to communicate more clearly with outside developers. Another participant warned that dropping EIP-8037 would prevent developers from deploying larger contracts and weaken the upgrade’s security goals.
Compatibility concerns had delayed testing since October, postponing the planned deployment to the public Hoodi testnet. Core developers planned to revisit the proposal on November 19. The foundation said Hoodi would remain on hold until the issues were resolved, and no Glamsterdam mainnet upgrade date had been confirmed.
