As reported on November 17, 2026, Ethereum’s planned Glamsterdam upgrade remained under review after developers raised concerns about its effects on existing contracts. The proposed deployment to the public Hoodi testnet had been postponed, and no mainnet upgrade date had been confirmed.
At a November 16 developer call, Ethereum Foundation developer Marius van der Wijden said Glamsterdam could affect as many as 15,000 on-chain automation programs—far more than earlier reviews had identified. Funds associated with potentially affected contracts were estimated at hundreds of thousands of dollars. These were estimates of possible exposure, not confirmed losses.
Security firm ChainSecurity’s Tanguy Rocher reported 152 findings, roughly half of which overlapped with the foundation’s internal research. Together, the reviews identified around 200 potential issues. In a separate review of approximately 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 the eight core technical assumptions about which the foundation had warned developers on November 6. The foundation had also identified three high-severity and at least 25 medium-severity defects in its external communications; most were being fixed.
Participants disagreed on how to proceed. Ansgar Dietrichs, a researcher involved in writing the proposal, argued for continuing the upgrade but acknowledged that core engineers needed to communicate more clearly with external developers. Other participants warned that dropping EIP-8037 would prevent developers from deploying larger contracts and weaken the upgrade’s security goals.
The November 16 call ended without agreement. Compatibility concerns had delayed testing since October. Developers planned to revisit the proposal on November 19, while the foundation said Hoodi would remain on hold until the issues were resolved. The November 17 report did not establish what that later meeting decided.