EIP-7762 Blob minimum base fee increase (Increase MIN_BASE_FEE_PER_BLOB_GAS)
No call decision · Fees & gas · EIP status Stagnant · created 2024-08-31
A proposal to raise the minimum blob base fee defined in EIP-4844 from 1 wei to 2^25, so that the price reaches its real level more quickly during demand surges.
Why it is needed
The minimum value of the blob base fee is currently 1 wei, which is very low. Because the base fee can rise by at most 1.125x per block even when blocks are full, once demand exceeds supply it takes an enormous number of blocks to climb the roughly eight orders of magnitude needed to reach the real market price. When EIP-4844 was designed, blobs were expected to enter a price discovery phase only about once, but in practice it has repeated many times, and as blob capacity approaches saturation and the roadmap calls for further capacity increases, this price discovery situation is expected to keep recurring. Raising the minimum to a more realistic level makes this process much faster.
What changes
Today
- MIN_BASE_FEE_PER_BLOB_GAS = 1 wei
- During demand surges, it takes an extremely large number of blocks for the base fee to rise to the real price
- Slow price discovery repeats every time blob capacity saturation recurs
After EIP-7762
- MIN_BASE_FEE_PER_BLOB_GAS = 2^25 wei (roughly 1 cent per blob at today's prices)
- Resets excess_blob_gas to 0 at the fork to prevent a base fee spike
- Speeds up how quickly the price reaches its real level during demand surges
Who is affected
- Rollup operators: Rollups that use blobs for data availability (DA) will need to readjust their blob posting strategy and pricing.
- Client implementation teams: Must add a block_timestamp argument to calc_excess_blob_gas and validate_block, and implement the fork-time reset logic.
- Ordinary users: Blob pricing does not change under normal conditions, but during demand surges the fee adjusts to the appropriate level more quickly.
In depth
Change to the MIN_BASE_FEE_PER_BLOB_GAS value
At its core, this specification changes MIN_BASE_FEE_PER_BLOB_GAS from 1 to 2**25. This is the floor the blob base fee can fall to; if blocks continue using less than the blob target, the base fee drops to this value.
Resetting excess_blob_gas to 0 at the fork
If the minimum base fee were raised immediately while excess_blob_gas stayed as-is, applying the new minimum to the formula could cause the blob base fee to spike all at once. To prevent this, the calc_excess_blob_gas function is modified so that if the parent block's timestamp is before FORK_TIMESTAMP and the current block's timestamp is at or after FORK_TIMESTAMP, it returns excess_blob_gas as 0. In all other cases, the existing calculation method is used unchanged.
Modification to validate_block
Since calc_excess_blob_gas needs the block timestamp to determine the fork point, validate_block is modified to pass block.header.timestamp as an additional argument when calling calc_excess_blob_gas to validate block.header.excess_blob_gas.
Why 2^25
With the base fee low, a simple transfer at a 1 gwei base fee costs about 5 cents at the ETH/USDC price at the time ($2,445.77). Using this price as the blob minimum price benchmark requires an excess_blob_gas of 63,070,646, and the amount needed to reach that value from 0 is calculated as 63070646/(3*2**17) = 160.396947225. The closest power of 2 to this is 2^27, but 2^25 was conservatively adopted to allow headroom in case the ETH price rises significantly. 2^25 corresponds to roughly 1 cent per blob at prices at the time.
Why it does not need to go lower than 2^25
Lowering MIN_BASE_FEE_PER_BLOB_GAS below 2^25 would not meaningfully lower blob prices while the network is unsaturated, but would slow price discovery once it saturates. The authors present a chart analyzing the share of blob base fee within type 3 transaction fees against historical L1 gas prices, explaining that even after the change, at historical L1 gas price levels, L1 gas price would have driven the blob price.
Backwards compatibility and security considerations
This EIP is not backward compatible and requires a coordinated hard fork where all clients upgrade simultaneously at a specific block number (the fork point). Rollups using blobs as a data availability layer must update their blob posting strategy to match the new minimum price.
Current status
This EIP's status is marked Stagnant. The materials currently available contain no record of a core developer call deciding on inclusion in a specific fork, so it cannot be confirmed from this document alone whether this proposal was actually adopted in a hard fork.