Blob Base Fee
The blob base fee is the dynamic price for blob data space in Ethereum, adjusted by supply and demand per EIP-4844.
Key Takeaways
- The blob base fee is a separate, dynamic price that blob transactions pay for data availability on Ethereum, operating independently from the regular gas fee market.
- It uses the same exponential adjustment mechanism as EIP-1559: when blob usage exceeds the per-block target the fee rises, and when usage falls below the target the fee drops, steering demand toward the target over time.
- Blob base fees directly determine rollup data-posting costs: during low-demand periods the fee can sit at its 1 wei floor, making L2 data publication nearly free, but demand spikes can push fees to thousands of gwei in minutes.
What Is the Blob Base Fee?
The blob base fee is the minimum price per unit of blob gas that a transaction must pay to include blob data in an Ethereum block. Introduced by EIP-4844 (Proto-Danksharding) in the Dencun upgrade (March 2024), it creates a dedicated fee market for blob data that is entirely separate from Ethereum's execution gas market.
Before EIP-4844, rollups posted their data as calldata, competing directly with smart contract execution for block space. This meant rollup costs rose whenever the network was congested, even if the congestion had nothing to do with data availability. The blob base fee solves this by giving data availability its own pricing lane: blob demand sets blob prices, and execution demand sets execution prices.
Like the regular base fee, the blob base fee is burned rather than paid to validators. This means block proposers earn no direct revenue from blob fees, keeping the mechanism aligned with Ethereum's deflationary EIP-1559 design.
How It Works
The blob base fee adjusts block by block using an exponential formula driven by a single state variable called excess_blob_gas. This variable tracks cumulative deviation from the target blob gas usage across all blocks.
The Update Rule
After each block, the protocol updates excess_blob_gas:
excess_blob_gas(N+1) = max(0,
excess_blob_gas(N)
+ blob_gas_used(N)
- TARGET_BLOB_GAS_PER_BLOCK
)If a block uses more blob gas than the target, excess grows and the fee rises. If a block uses less, excess shrinks and the fee falls. The fee itself is computed from the accumulated excess:
blob_base_fee = MIN_BASE_FEE_PER_BLOB_GAS
* e^(excess_blob_gas / BLOB_BASE_FEE_UPDATE_FRACTION)The exponential function means the fee adjusts slowly near the target but accelerates when demand persistently deviates. This mirrors the EIP-1559 mechanism for execution gas, which caps the per-block change at roughly 12.5%.
Key Constants
EIP-4844 defined the original Dencun-era parameters. The Pectra upgrade (May 2025) revised them via EIP-7691:
| Parameter | Dencun (EIP-4844) | Pectra (EIP-7691) |
|---|---|---|
| GAS_PER_BLOB | 131,072 (2^17) | 131,072 (unchanged) |
| Target blobs per block | 3 | 6 |
| Max blobs per block | 6 | 9 |
| TARGET_BLOB_GAS_PER_BLOCK | 393,216 | 786,432 |
| BLOB_BASE_FEE_UPDATE_FRACTION | 3,338,477 | 5,007,716 |
| MIN_BASE_FEE_PER_BLOB_GAS | 1 wei | 1 wei |
The update fraction was recalculated for the new maximum (9 blobs) so that a full block still raises the fee by approximately 12.5%. With a higher target, the fee drops more aggressively when blocks are underfull, keeping blob space cheap as long as demand stays below target.
Relationship to Regular Gas
A blob transaction (type-3 transaction) pays two fees: the regular execution gas fee for its EVM operations, and a separate blob gas fee for its attached blobs. Each blob consumes exactly 131,072 units of blob gas, priced at the current blob base fee. The two fee markets are independent: a spike in DeFi activity raises execution gas costs but does not affect blob prices, and vice versa.
Blob transactions can also set a max_fee_per_blob_gas field, which caps the blob base fee they are willing to pay. If the current blob base fee exceeds this cap, the transaction is not included. This works analogously to maxFeePerGas in regular EIP-1559 transactions.
Why It Matters for Rollup Economics
The blob base fee is the single most important variable in rollup operating costs. Layer 2 networks like Arbitrum, Optimism, and Base post compressed transaction batches as blobs. When the blob base fee is at its floor of 1 wei, posting a 128 KB blob costs a fraction of a cent. When demand spikes, costs can surge by orders of magnitude within minutes.
This creates a distinctive economic pattern for rollups: long periods of near-free data posting interrupted by brief, sharp fee spikes when multiple rollups compete for limited blob space. For a deeper analysis of these dynamics, see the research article on EIP-4844 and the blob fee market.
Historical Blob Base Fee Behavior
Since the Dencun activation in March 2024, the blob base fee has shown extreme variance:
- For most of its early history (March through October 2024), the blob base fee sat at or near the 1 wei minimum. Average blobspace costs rarely exceeded $0.01 per blob on a weekly basis during this period.
- When rollup adoption picked up and blocks consistently exceeded the 3-blob target, the exponential mechanism drove the fee up rapidly. The fee can double in just a few blocks when every block is full.
- Pectra's target increase to 6 blobs (May 2025) temporarily reset the fee to its floor by doubling the available supply. In the first week post-Pectra, average blob usage ran roughly 33% below the new target, making blobs virtually free again.
The Pectra and Fusaka Impact
The Pectra upgrade (May 7, 2025) was the first major change to blob parameters. By raising the target from 3 to 6 blobs and the maximum from 6 to 9, EIP-7691 doubled the supply of cheap blob space. It also adjusted the update fraction so that the fee adjusts more gently per block when blobs are scarce (falling roughly 14.5% per empty block) while still rising about 8.2% when every slot is full.
The Fusaka upgrade (December 2025) introduced PeerDAS (peer-based data availability sampling), which removes the requirement for every node to download every blob. With PeerDAS, Ethereum can raise blob limits further without increasing bandwidth requirements proportionally. This paves the way for significantly higher blob targets through lightweight "blob parameter only" (BPO) forks between major upgrades.
Use Cases
Understanding the blob base fee is essential for several participants in the Ethereum ecosystem:
- Rollup operators monitor the blob base fee continuously to decide when to post batches. Some implement fee-aware batching: accumulating transactions during fee spikes and posting when the fee drops back toward the floor.
- Rollup users experience the blob base fee indirectly through L2 transaction fees. When blob costs spike, L2 sequencers pass the increased data-posting cost through to users as higher fees.
- MEV searchers and block builders factor blob base fees into inclusion decisions. Because blob gas and execution gas are priced independently, builders optimize both dimensions when constructing blocks.
- Protocol researchers study the blob fee market to calibrate future parameter changes: target count, update fraction, and minimum fee all affect rollup economics and network sustainability.
Comparison with the Execution Base Fee
The blob base fee and the execution base fee share the same EIP-1559 exponential adjustment design, but they differ in important ways:
| Property | Execution base fee | Blob base fee |
|---|---|---|
| Resource priced | Computation and storage | Data availability (blobs) |
| Floor | No protocol-level floor | 1 wei per blob gas |
| Data retention | Permanent (calldata) | Temporary (~18 days) |
| Destination of fees | Burned | Burned |
| Priority fee (tips) | Yes, paid to validators | No separate blob tip |
The lack of a priority fee for blobs means there is no way to "jump the queue" for blob inclusion by tipping validators. Blob inclusion is purely a function of whether the transaction meets the current blob base fee and whether the block has remaining blob capacity.
Risks and Considerations
Fee Volatility
The exponential adjustment mechanism can cause the blob base fee to spike by orders of magnitude within minutes during sustained high demand. A sequence of full blocks (each at the maximum blob count) compounds the fee exponentially. Rollups that cannot defer posting risk absorbing these spikes, translating them into sudden L2 fee increases for end users.
Target Manipulation
Large rollups that consistently submit near-target blob volumes have outsized influence on the fee. If a single operator submits enough blobs to push usage above target, all other blob submitters pay higher fees. This creates a form of negative externality where one rollup's activity raises costs for all others.
Minimum Fee Floor Debate
The 1 wei minimum means that during low-demand periods, blob space is essentially free. While this benefits rollups, it raises questions about whether validators and the network are adequately compensated for carrying blob data. EIP-7762 proposed raising the minimum to 2^25 wei (roughly 33 million wei) to establish a meaningful floor, and EIP-7918 proposed bounding the blob base fee by execution cost so that blob transactions always pay a reserve price relative to their calldata-equivalent cost.
Temporary Data Availability
Blob data is pruned from the network after approximately 18 days. The blob base fee prices access to this temporary data availability window, not permanent storage. Applications that need data beyond this window must arrange their own archival, adding an infrastructure cost that the blob base fee does not cover.
For a broader view of how the blob fee market fits into Ethereum's data availability strategy, see the glossary entries on blob fee market, blob sidecar, and full danksharding. For analysis of how these dynamics affect Layer 2 profitability, see the research on blob surplus and L2 profitability.
This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.