Wallet custody, cryptographic trust boundaries, vulnerabilities, audits and practical defensive habits

Glamsterdam compatibility review raises concerns for existing Ethereum contracts

Developers responsible for existing Ethereum contracts may need to check how the proposed Glamsterdam upgrade could affect them. In reporting published on November 17, 2026, Foresight News cited CoinDesk on a November 16 developer call at which Ethereum Foundation developer Marius van der Wijden said the upgrade could affect as many as 15,000 on-chain automation programs. The funds associated with potentially affected contracts were estimated at hundreds of thousands of dollars. These are estimates of potential exposure, not confirmed losses.

The review is broader than earlier checks had identified. ChainSecurity’s Tanguy Rocher reported 152 findings, about half of which overlapped with the Foundation’s internal research, bringing the combined count to roughly 200 potential issues. In a separate review of approximately 25,000 contracts with unusual gas usage, Dedaub flagged 70 medium- or high-risk issues; 22 had previously been missed by the Foundation. Most problems stemmed from two of the eight core technical assumptions about which the Foundation had warned developers on November 6. Through its own external communications, the Foundation identified three high-severity and at least 25 medium-severity flaws, most of which were being fixed.

The November 16 call reached no agreement on how to proceed. Researcher Ansgar Dietrichs, who helped write the proposal, favored moving forward 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.

Compatibility concerns had delayed testing since October, including 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.

Further reading