EIP-8059 Gas unit rebase for high-precision measurement (Gas Units Rebase for High-precision Metering)

No call decision · Fees & gas · EIP status Draft · created 2025-10-22

A proposal that scales up every gas-related constant and variable by 1000x (REBASE_FACTOR), allowing operation costs to be priced precisely without introducing fractional gas.

Why it is needed

In today's EVM, pure computation instructions such as addition and multiplication (ADD, MUL, etc.) are significantly underpriced relative to instructions that read and write state (SSTORE, SLOAD, etc.). This is because client optimizations and hardware advances keep making computation faster, while state access performance keeps worsening as Ethereum's state grows, and this trend is expected to continue. So proposals have emerged to reprice computation instructions cheaper and state instructions more expensive, but there is an obstacle. Since gas is an integer unit, pricing computation instructions cheaply causes a rounding error where costs that should truly be less than 1 all round up to 1, and this error reduces the number of operations that fit in a block, hurting scalability. Conversely, pegging the fastest instruction to 1 gas and raising everything else would sharply cut throughput under the current block limit. This proposal scales up the gas unit itself by 1000x to eliminate this rounding error without major changes to internal EVM logic.

What changes

Today

After EIP-8059

Who is affected

In depth

Rebase constant and scope of application

REBASE_FACTOR is 1000. All gas-related parameters and variables scale up by this factor. Per the Motivation section, at this scale of rebase, every opcode's cost becomes significantly more expensive, but transaction-level and block-level gas limits rise by the same factor. Introducing fractional gas would complicate EVM gas computation, so the approach taken instead is to scale up the unit itself while keeping integer units.

Base fee calculation at the fork boundary

At the fork boundary, calculate_base_fee_per_gas is updated so that its inputs, parent_gas_used and parent_base_fee_per_gas, are also scaled by REBASE_FACTOR. This is a measure to carry the last pre-rebase block's values over into the new unit system.

Rounding error analysis: why a large rebase is needed

Since computation opcodes only affect block execution time, the overall Mgas/s throughput of computation opcodes is set by which opcode is chosen as the pricing anchor. Per the execution time estimates in EIP-7904, anchoring EcRecover at its current price (3000 gas) yields 175 Mgas/s. At a 50 Mgas/s anchor (a 100M gas limit assuming 2 seconds of block execution), the average rounding error is 59.3%, meaning that without integer rounding, opcodes could on average be priced 59.3% cheaper. Only once the anchor exceeds 400 Mgas/s does the rounding error become sufficiently small.

The basis for the 1000x figure

The source cites two advantages of the 1000x factor. First, it is large enough to fully eliminate today's computation opcode rounding error and provide headroom for the future. At a 400 Mgas/s anchor the error shrinks sufficiently, and assuming 2 seconds of block execution time this implies an 800M gas block limit, a 22x increase over the current 36M limit. Second, reasoning about the new unit becomes easier: block limits and targets move from millions to billions, while gas costs move from units of 1 to units of 1000.

Backwards compatibility and security considerations

Since this proposal is a backward-incompatible gas repricing, a scheduled network upgrade is required. On the security side, it notes that higher costs for state access operations may affect the usability of certain applications, and that the effects on various dapps and user behavior need further analysis. It also notes that the increased magnitude of gasLimit and gasUsed grows the block header's RLP representation by 2 bytes, and the bandwidth impact requires further analysis.

Progress status

This EIP is in Draft status, created on October 22, 2025. Being still at the draft stage, figures and specifications may change, and there is no core developer call decision yet on inclusion in a specific fork.

Original EIP · ← EIPs