In an Ethereum Foundation blog post, Marius van der Wijden asked developers and auditors to examine eight gas assumptions affected by proposed upgrade changes, CryptoSlate reported. The EIP-8037 gas rules are part of the proposed Glamsterdam upgrade and would meter growth in persistent state separately from execution, according to CryptoSlate.

The review matters for applications that reimburse transaction costs or rely on wallet authorizations: CryptoSlate reported that some relayers could recover too little while certain failed transactions could expose reusable authorizations. The authorization risk depends on the failure and the authorization's remaining validity, the publication said.

Ethereum core developers want application teams to help assess whether the proposals need revision because internal audits cannot cover every contract and off-chain service, according to CryptoSlate. The outlet reported that ChainSecurity and Dedaub are also investigating, alongside internal reviews, and that projects are being asked how affected systems could be repaired.

How EIP-8037 gas rules affect relayers

The proposed EIP-8037 gas rules would increase the cost of creating persistent blockchain data, while a separate proposal, EIP-8038, would change prices for accessing and writing existing state, CryptoSlate reported. The stated aim is to support greater throughput while controlling the data Ethereum nodes must retain, the publication said.

Under EIP-8037 gas rules, a transaction with a gas limit above 16,777,216 initially funds a separate state-gas reservoir, according to CryptoSlate. State creation would draw first on that pool and then on execution gas, the outlet reported.

A relayer pays to execute a transaction for another party and may calculate reimbursement by measuring gas before and after the work, CryptoSlate reported. Solidity's gasleft() reading excludes the reservoir, so the difference between two readings can miss costs the relayer actually pays, according to the publication.

If the later reading exceeds the earlier one, checked subtraction reverts and blocks the operation, CryptoSlate reported. With unchecked subtraction, the result can wrap into a large number and potentially lead to excessive reimbursement, depending on the surrounding arithmetic and payment checks, according to the outlet.

The billing guidance suggests agreeing on a user-signed fee based on an estimate under the new rules, CryptoSlate reported. Where metering is still needed, clamping the subtraction and capping payment at a signed maximum can limit the charge, although reservoir-funded costs remain outside the measurement, the publication said.

An open specification proposal, PR #12581, would prevent gas readings from increasing, according to CryptoSlate. The outlet reported that this would address the subtraction issue but would not eliminate the billing blind spot for reservoir spending.

Wallet delegation and failed transactions

The review also examines EIP-7702 delegation, in which an account authorizes delegated contract code, CryptoSlate reported. According to the publication, a transaction can still enter a block under the proposed EIP-8037 gas rules if it runs short of gas during pre-execution, even as its delegation and the authorization-related update to the account nonce are rolled back.

An exposed authorization can then be reused if it still passes its validity checks, including the authorizing account's nonce, CryptoSlate reported. The outlet said an attacker could use a single transaction both to apply that authorization and to initialize ownership if the delegated contract has an initializer allowing the first caller to choose its owner.

Authorization front-running already existed in public mempools, but the proposed failure scenario can expose a reusable authorization after a failed mined transaction even when it was submitted privately, according to CryptoSlate. The publication also reported that delegations applied before the top-level execution frame remain in place if that later frame fails.

A failed receipt therefore calls for checking the account's resulting code and nonce, CryptoSlate reported. Suggested safeguards include tying initialization to the account's signature or self-calls and invalidating exposed authorizations; a separate suggestion to charge the worst-case authorization cost upfront remains unadopted, according to the outlet.

Storage prices and retry paths

Under the proposed EIP-8037 gas rules, creating a cold storage slot would cost 110,020 total gas, compared with 22,100 under Osaka, CryptoSlate reported. Of the proposed total, 12,100 would be execution gas and 97,920 would be state gas, with the reservoir determining which balance funds the latter, according to the publication.

The eight-part framework separates three price assumptions, including fixed budgets and reserves, from five accounting assumptions concerning gas returns, failure handling, billing and delegation, CryptoSlate reported. The distinction gives application teams different aspects of their systems to examine, according to the outlet.

Research cited by CryptoSlate shows that changed costs and returned gas can allow a contract to finish while recording an underfunded operation as permanently unsuccessful. The publication reported that a valid operation may no longer be repeatable if the record eliminates its retry path; revalidating budgets, propagating failures and preserving retries each address different parts of that risk.

Project fixes and activation

The repository asks affected projects whether a settings change, upgrade or migration could fix their problem and roughly when, CryptoSlate reported. According to the publication, developers will use those answers to weigh applications' capacity for compatibility work and identify places where changes to the specification could prevent damage.

Concrete reports about breakage and repairs will feed into the next specification discussions on the EIP-8037 gas rules, CryptoSlate reported. Hoodi's activation remains postponed, while the notices leave mainnet activation unset, according to the outlet.

Conclusion

The proposed changes would separate state-growth metering from execution and could alter calculations used by applications and relayers, CryptoSlate reported. The outlet also identified a conditional wallet-authorization risk and contract failure-handling issues that teams are being asked to examine. Developers' next concrete step is to use project reports on what breaks, how it can be repaired and roughly when fixes are possible in further specification discussions, according to CryptoSlate. Hoodi activation remains postponed and mainnet activation is unset, the publication reported.

Frequently Asked Questions

How could EIP-8037 change Ethereum relayer billing?

CryptoSlate reported that relayers using differences between gasleft() readings could miss state-gas reservoir costs they actually pay. The billing guidance suggests that users sign a fee calculated from an estimate using the proposed rules. If metering is still required, a charge can be limited by clamping the subtraction and setting a maximum payment signed by the user, according to the publication.

What is the 16,777,216 gas threshold in EIP-8037?

CryptoSlate reported that transactions whose gas limits are higher than 16,777,216 initially fund a separate reservoir for state gas. Under the proposal, state creation draws from that reservoir first and then from execution gas. Solidity's gasleft() reading excludes the reservoir, according to the publication, which matters for applications measuring gas to calculate reimbursement.

How could EIP-8037 affect EIP-7702 wallet authorizations?

Insufficient gas during pre-execution can leave a transaction in a block while rolling back delegation and an authorization-related nonce update, CryptoSlate reported. An exposed authorization that still satisfies its validity checks can then be reused. The outlet reported that suggested safeguards would tie initialization to the account's signature or self-calls and invalidate authorizations that have been exposed.

When will the Glamsterdam changes activate on Hoodi and mainnet?

Hoodi's activation remains postponed, and the notices leave mainnet activation unset, CryptoSlate reported. Projects are being asked to report whether settings changes, upgrades or migrations could repair affected systems and roughly when. Those reports will inform the next specification discussions, according to the publication.