For anyone relying on an automated Ethereum contract, the concern raised by the planned Glamsterdam upgrade is compatibility—not a confirmed loss of funds. As reported on November 17, 2026, Ethereum Foundation developer Marius van der Wijden told a November 16 developer call that the upgrade could affect as many as 15,000 on-chain automation programs. The funds tied to potentially affected contracts were estimated at hundreds of thousands of dollars. The number of programs was far greater than earlier reviews had identified.
The review is still uncovering potential problems. 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 issues stemmed from two of eight core technical assumptions about which the foundation warned developers on November 6.
The foundation also identified three high-severity and at least 25 medium-severity flaws in its external communications. Most were being fixed. These are reported findings and estimates, not confirmed losses.
The November 16 call ended without agreement. Researcher Ansgar Dietrichs, who helped write the proposal, argued that the upgrade should proceed but acknowledged that core engineers needed to communicate more clearly with external developers. Other participants warned that removing 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 on the public Hoodi testnet. 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.