Ethereum Developers Urge dApps to Test EIP-8037 Gas Changes

Ethereum core developers are asking application teams and auditors to help determine whether proposed modifications in the Glamsterdam upgrade need revision. Because internal evaluations and external reviews by security firms cannot cover every individual project, developers are being asked to check how their smart contracts and off-chain services handle new cost structures.

In a recent blog post, Marius van der Wijden outlined eight gas assumptions affected by the upcoming changes. These adjustments include EIP-8037, which raises the cost of creating persistent blockchain data and meters state growth separately from general execution. Meanwhile, EIP-8038 alters how developers access and write to existing blockchain state. The goal of these proposals is to support higher transaction throughput while controlling the total amount of data that nodes must retain.

The proposed rules introduce complex accounting hurdles for decentralized applications. For instance, relayers that pay transaction costs on behalf of users may find their reimbursement calculations disrupted. Under the new rules, transactions with high gas limits fund a separate state-gas reservoir. Because Solidity reading functions exclude this reservoir, subtracting two gas readings can fail or result in incorrect billing.

Ethereum projects must evaluate new gas assumptions and report potential fixes before the upgrade proceeds.

Additional complications arise with EIP-7702 delegation. Insufficient gas during pre-execution can cause a transaction to be included in a block while rolling back its authorization-related sequence updates. This leaves an exposed authorization potentially open to reuse by an attacker if initialization rules allow it. Suggested safeguards include binding account signatures and invalidating exposed authorizations.

Understanding eip-8037 and State Growth

Creating a cold storage slot under the proposed schedule carries a significantly higher total cost compared to previous standards, split between execution gas and state gas. Security research indicates that these changed costs can occasionally cause an operation to record as permanently unsuccessful, removing retry paths for valid transactions.

Why it matters

This call for review affects all developers building decentralized applications on Ethereum, as they must determine whether their current billing systems, relayers, and wallet integrations can adapt to separate state metering. Project teams need to report whether upgrades, migrations, or setting adjustments can fix these vulnerabilities. These concrete findings will help shape the final specifications of the Glamsterdam upgrade and prevent unintended disruptions across the network.