Skip to content
News briefET-2026-0459

Reprice gas for new contracts and leave the old ones alone

A draft EIP would apply Glamsterdam's new gas schedule only to newly deployed contracts, through a separate V2 opcode set.

2 minEthereum & Layer-2

A draft Ethereum Improvement Proposal submitted on 8 November offers a way out of a dilemma facing the Glamsterdam upgrade. EIP-8037 and EIP-8038 would reprice state access and support a much higher gas limit, but applying the new schedule to every contract risks breaking or griefing existing ones that depend on today's gas costs, while deferring them postpones the state-growth controls. EIP-8488, titled Versioned Opcodes for Gas Repricing, proposes a third option: reprice only new code.

The mechanism is a parallel V2 opcode set. For every opcode whose cost or observable gas accounting changes under the two repricing EIPs, a V2 counterpart is defined, such as SSTORE_V2, CALL_V2 and CREATE2_V2. After activation, newly deployed runtime bytecode is scanned, and deployment fails if it contains a legacy opcode that has a V2 counterpart. Accepted contracts get a code_version field set to 2. Contracts already on chain keep the pre-Glamsterdam schedule indefinitely.

Two details carry most of the design. A new DELEGATECALL_V2 succeeds only if its target also has code_version 2, so new code cannot quietly run legacy logic under the new schedule. And the gas-introspection opcodes GAS and GASLIMIT are left out of the V2 set entirely, to stop new contracts from encoding assumptions about gas accounting that a future repricing would invalidate; the draft leaves replacements such as standard out-of-gas signalling to companion proposals.

The argument for the approach is gradualism: as upgradeable systems replace their implementations, the share of execution under the old schedule should fall, and the gas limit could rise step by step as V2 adoption grows. The proposal is a draft from an outside contributor, awaiting review by EIP editors, and it is one of several ideas for the same problem.

Retold from GitHub, ethereum/EIPs. This is a summary in our own words; follow the link for the original reporting.

Questions

What does EIP-8488 propose?
A V2 opcode set that carries the EIP-8037 and EIP-8038 gas schedule. Contracts deployed after activation may use only V2 opcodes, while existing contracts keep the pre-Glamsterdam schedule indefinitely.
Why would EIP-8488 remove the GAS opcode?
The draft omits gas-introspection opcodes such as GAS and GASLIMIT from the V2 set, so new contracts cannot build in assumptions about gas accounting that a future repricing would break.

Read next

Across the network

Desks that share a zone with this one on the BITBRIEF coverage map.

Terms defined