Ethereum developers flag contracts at risk from gas changes
Ethereum developers warned on Aug. 24 that planned gas changes in the Glamsterdam upgrade could disrupt a small group of Layer 1 smart contracts.
- Ethereum developers warned Glamsterdam gas repricing could break a small group of Layer 1 contracts.
- EIP-8037 raises state-creation costs, while EIP-8038 reprices storage and account access across Ethereum’s execution layer.
- Most flagged failures can be resolved by increasing transaction gas limits, according to Ethereum developers.
- Contracts using 2,300-gas stipends, fixed call limits or gasleft logic face the greatest compatibility risks.
- Developers can test contracts immediately on Platåberget before public testnet and eventual mainnet deployment begins.
The Ethereum Foundation urged developers to test contracts and update fixed gas assumptions before mainnet activation.
The warning concerns EIP-8037 and EIP-8038, which are scheduled for inclusion in Glamsterdam. Developers said most contracts remained unaffected during transaction replays, while many flagged cases could be corrected by raising their gas limits.
Ethereum gas repricing changes state costs
EIP-8037 changes how Ethereum charges for creating state, including new accounts, storage slots and deployed contract bytecode. It introduces separate state-gas accounting intended to prevent rapid blockchain-state growth as Ethereum increases network capacity.
EIP-8038 raises costs for accessing existing state. The proposal covers operations including SLOAD, SSTORE, cold account access, EXTCODESIZE and EXTCODECOPY.
Ethereum developers last broadly adjusted state-operation prices during the Berlin upgrade in 2021. Since then, Ethereum’s state has expanded, while validators have supported higher block gas limits.
The Ethereum Foundation said repricing resource-heavy operations is necessary before the network can safely raise capacity further. Developers designed the new schedule around a performance target that could support roughly three times the current base throughput.
Hardcoded gas assumptions create compatibility risks
Developers replayed historical Ethereum mainnet transactions under Glamsterdam’s proposed pricing schedule. They sorted the results into unchanged transactions, successful transactions with different gas usage, failures fixable through higher limits and potentially broken transactions.
The last group continued to fail even after researchers raised the supplied gas substantially. The Foundation’s warning identified fixed gas stipends, hardcoded call limits, logic based on gasleft() and presigned transactions with fixed limits as recurring risk factors.
Contracts that use Solidity’s historical 2,300-gas stipend through transfer or send may require particular attention. Operations that previously completed within that allowance may consume more gas under the new state-access schedule.
The Foundation has not publicly identified every affected application. It said direct outreach to the most affected builders was already underway and described the potentially broken group as small.
Wallets and gas estimators also require updates
The warning extends beyond smart contracts. Wallets, RPC providers, indexers and node tools must update their gas-estimation systems to recognize the revised cost rules.
Software using cached constants could underestimate the gas needed for a transaction and cause it to fail. Both proposals require tools using eth_estimateGas and related functions to account for the revised state costs.
As crypto.news previously reported, Glamsterdam could also disrupt wallets and gas tools that assume ordinary transfers always require 21,000 gas. Transfers to existing accounts retain that figure, while transfers creating new accounts will incur an additional state charge.
Regular users do not need to make manual changes, according to the Foundation. Updated wallet and infrastructure providers should apply the necessary gas estimates automatically.
Developers can test fixes on Platåberget
Ethereum developers launched the Platåberget testnet to provide a long-running environment for Glamsterdam testing. The network, also called glam-devnet-8, already runs the new repricing schedule.
Contract maintainers can enter an address into Ethereum’s checker to identify historical transactions that diverge under the proposed rules. Developers should raise supplied gas limits when that resolves the issue or review individual call sites when failures persist.
In related coverage, Ethereum’s Glamsterdam work has moved Layer 1 scaling back into focus through gas repricing, block-level access lists and changes to block construction.
The next stage will involve additional devnet testing, followed by forks on Sepolia and Hoodi. Ethereum’s roadmap targets Glamsterdam for Q4 2026, but developers have not announced a fixed mainnet activation date. The final schedule depends on stable client implementations and successful public-testnet deployments.