
Several prominent developers are urging core developers to halt the Ethereum Glamsterdam upgrade in its current form, warning that its planned gas changes could break smart contracts that hold user funds. As reported by CoinDesk, the founder of Curve Finance wrote "Please don't break the chain. It does look like the Glamsterdam upgrade would lead to another emergency hard fork back, with a lot of drama." A prominent DeFi developer called the plan "completely ridiculous," while another developer noted his team had found the same issues before Glamsterdam went live on the Sepolia testnet. The opposition has even changed minds among Ethereum Glamsterdam supporters, with an influential community member who initially called for "asap" activation reversing course hours later, stating "We should (clearly, now) not continue towards Glam activation asap. I was wrong to say so."
The Ethereum Foundation has issued a formal warning to developers and auditors on November 6 (UTC+8) to review their smart contracts for dependencies on eight gas pricing assumptions that will no longer hold after the Gas fee adjustments introduced by EIP-8037 and EIP-8038 in the Glamsterdam upgrade. According to the latest reports from ME News, the foundation has established a code repository providing explanations, examples, and checklists for each assumption, enabling self-auditing capabilities for affected projects. The warning comes as the Hoodi hard fork remains on hold until identified compatibility concerns are resolved, while development of Ethereum's subsequent Hegota upgrade continues without interruption. As reported by CoinDesk, Ethereum developer Marius van der Wijden posted that an audit by security firm ChainSecurity found some projects rely on gas-billing invariants that EIP-8037 and EIP-8038 could break in the Glamsterdam upgrade, potentially creating smart contract compatibility issues.
Ethereum developers Leo Glisic and Giulio Rebuffo have submitted competing proposals on Sunday, November 8, offering different approaches to prevent Glamsterdam's revised gas pricing from disrupting existing smart contracts. Glisic's proposal, EIP-8488, would introduce a separate set of instructions for newly deployed smart contracts while allowing older contracts to continue operating under their existing gas rules. Under this proposal, new contracts would use V2 opcodes that follow the revised pricing introduced through EIP-8037 and EIP-8038, while existing contracts would retain the original pricing structure. Rebuffo has suggested a different solution in a separate draft that would introduce two gas accounting systems within each transaction. One would calculate how much gas a contract consumes under the previous rules, preserving the conditions it expects during execution, while the second would calculate the actual transaction fee using the revised pricing schedule. His proposal acknowledges that no execution client implementation or consensus tests have yet been completed for the design, and neither proposal has been approved for inclusion in Glamsterdam.
The security concerns were detailed in an October 13 analysis by ChainSecurity, which examined how Glamsterdam could change the behavior of contracts that continue executing after an external call fails. Under Ethereum's existing rules, some contracts depend on a failed operation leaving too little gas for subsequent instructions to complete. According to the Ethereum Foundation, fixed gas budgets and gas reserves are the most common issues found so far, particularly in contracts that depend on predetermined transaction costs. The identified risks include contracts that assume gas consumption can only move in one direction, fixed gas allowances will remain sufficient, or reverted calls cannot return gas already spent on creating state. The Ethereum Foundation has published a GitHub repository documenting eight affected invariants with explanations, examples and instructions for developers to examine their own code. As reported by Crypto.news, pseudonymous developer banteg warned on X that an existing analysis had already identified roughly 200,000 potentially affected contracts, while methodological problems could mean the actual number is higher. The concerns extend to the deployment and operation of several prominent protocols, rather than being limited to isolated coding mistakes.
Ethereum developers postponed the October 26 Hoodi activation after concerns emerged about how the revised gas rules could affect contracts already deployed on the mainnet. The postponement covered the Amsterdam execution layer changes, Gloas consensus changes and a planned increase in Hoodi's gas limit to 200 million. In a November 6 statement, Ethereum Foundation developer Marius van der Wijden said the organization was working with ChainSecurity and Dedaub to examine affected applications and gather feedback from developers. A subsequent private Glamsterdam test had been tentatively discussed for November 16 to 20 at the earliest during an October 29 developers' meeting, though this schedule was drawn up before the two competing proposals were submitted. The delay coincides with Ethereum ETFs logging their worst month for flows since launch, creating additional pressure on core developers to address the compatibility concerns before proceeding with the upgrade. As reported by ME News, the Foundation's November update describes the hold as addressing findings about how applications behave when a transaction runs low on gas, with developers working through issues identified during the gas review process.