Ethereum’s Glamsterdam testing has highlighted a difficult part of protocol engineering: changing resource prices can affect smart contracts that were written under older assumptions. In a November 6 research update, the Ethereum Foundation said ChainSecurity had identified projects that could be vulnerable after EIP-8037 and EIP-8038 alter how gas is charged for certain operations and state.
Gas is more than a transaction fee
Users generally encounter gas as the fee paid to execute a transaction. For developers, however, gas is also part of the execution environment. Contracts may make decisions based on available gas, call other contracts, or rely on assumptions about how much computation and storage operations cost. A change to the gas schedule can therefore influence contract behavior.
What the EIPs are changing
The Ethereum Foundation describes EIP-8037 and EIP-8038 as changes to gas charging for operations and state. The goal is connected to Glamsterdam’s broader effort to make resource costs more sustainable. The precise impact depends on the operation and contract design; it would be inaccurate to say that every contract becomes vulnerable or that all transaction fees necessarily rise.
Why invariants matter
An invariant is a condition a program expects to remain true. Smart contracts often use assumptions about execution costs to reason about whether a sequence of operations can complete. If the protocol changes the cost of an operation, a contract may no longer behave as its author expected. The code can remain byte-for-byte identical while the environment around it changes.
Testing before activation
The Foundation said the findings led developers to delay the Hoodi fork process until the issues are resolved. This is a testnet decision, not evidence that the changes have already affected Ethereum mainnet. Testnets let researchers identify compatibility problems before production users and assets are exposed.
What developers should review
Teams should identify gas-sensitive logic, unusual low-level calls, assumptions about remaining gas and interactions with external contracts. Tests should include boundary conditions rather than only normal successful transactions. Auditors can also review whether a contract depends on a specific gas schedule and whether a protocol change could invalidate that dependency.
Lessons for the wider blockchain industry
Smart contracts are deployed into environments that evolve. Protocol teams must balance performance and sustainability improvements with the need to preserve predictable execution. The Ethereum episode illustrates why compatibility analysis requires more than testing client software: developers need to examine the behavior of real applications under changed protocol rules.
Conclusion
EIP-8037 and EIP-8038 underline the security implications of gas repricing. The pause in Hoodi testing gives developers time to understand affected assumptions and address risks before activation. Application teams should follow official updates and test against the latest specifications rather than relying on old gas-cost expectations.