How the Blob Fee Market Works on Ethereum After Dencun

The blob fee market is a separate, independently priced market for a new type of data storage called "blobs," introduced by EIP-4844 (also known as proto-danksharding) in Ethereum's March 2024 Dencun upgrade. Blobs are priced using their own supply-and-demand mechanism, distinct from the regular gas market that prices computation and standard transaction data — meaning blob prices can spike or stay cheap independently of how busy Ethereum's regular gas market is.

Why blobs exist

Before EIP-4844, layer 2 rollups had to post their transaction data to Ethereum as regular "calldata" inside normal transactions, competing directly with everyone else for the same gas market. This made posting data expensive, since calldata was priced the same as computationally expensive operations, even though data meant only for temporary availability doesn't need to be processed the same way a smart contract call does.

Blobs solve this by giving rollups a dedicated, cheaper data channel. A blob is a chunk of data (roughly 128 KB) attached to a block but not accessible to the EVM — smart contracts can't read blob contents directly, only a cryptographic commitment to it. Nodes only need to store blobs temporarily (currently around 18 days, sufficient for rollups to have time to pull the data and prove it if needed) rather than permanently, unlike ordinary chain state.

How blob pricing works

Each block has a target number of blobs and a maximum number of blobs it can include. If usage is below the target, the price per blob trends down over time; if usage consistently exceeds the target, the price trends up — this is structurally similar to EIP-1559's base fee mechanism for regular gas, but calculated and adjusted entirely separately.

Aspect	Regular gas (EIP-1559)	Blob gas (EIP-4844)
What it prices	Computation and calldata	Blob data attached to a block
Base fee adjustment	Rises/falls based on block fullness relative to target	Rises/falls based on blob count relative to target, independently
Paid in	ETH, denominated in gas	ETH, denominated in a separate "blob gas" unit
Burned or kept by validators	Base fee burned, priority fee to proposer	Base fee burned, same principle
Data availability window	Permanent (state) or indefinite (calldata, part of history)	Roughly 18 days, then pruned
Who mainly uses it	Any transaction	Primarily rollups posting batch data

Because the two markets are priced separately, a period of heavy regular-transaction demand (say, a popular NFT mint) doesn't necessarily make it more expensive for rollups to post blob data, and vice versa — a surge in rollup activity doesn't necessarily spike gas fees for someone doing a plain ETH transfer.

Why this matters for L2 costs

For layer 2 users, the practical effect has been a significant reduction in transaction fees on rollups like Arbitrum, Optimism, and Base, because the cost of posting their batched transaction data back to Ethereum — previously a major component of L2 fees — dropped substantially once that data could go into cheap, purpose-built blobs instead of expensive calldata. This is one of the clearest examples of a base-layer Ethereum upgrade directly lowering costs for DeFi users operating on L2s, without those users needing to do anything differently.

That said, blob space is not unlimited, and during periods of high rollup activity across many L2s simultaneously, blob fees can rise just like regular gas fees can during network congestion — it's a separate market, not an infinite-capacity one.

The bigger roadmap: full danksharding

EIP-4844 is explicitly a stepping stone, hence "proto-danksharding." The long-term vision, full danksharding, involves significantly increasing the number of blobs per block and introducing data availability sampling — where nodes can verify data is available without downloading all of it — to scale blob capacity much further while keeping node requirements manageable. Getting there involves more research and engineering work, including improvements tied to efficient proofs similar to those discussed in our piece on light clients.

How rollups actually use blobs

From a rollup operator's perspective, the workflow changed relatively little at a high level, even though the underlying cost structure shifted substantially. A rollup still periodically batches up many users' transactions and posts a compact summary back to Ethereum — what changed is that this batch data now typically goes into one or more blobs attached to a transaction, rather than being encoded directly as calldata within the transaction itself. The transaction still contains a cryptographic commitment referencing the blob's contents, which is what lets the rollup's fraud-proof system (for optimistic rollups) or validity-proof system (for ZK-rollups) verify the posted data is correct, without the EVM itself needing to read the blob's full contents directly.

Monitoring blob usage

Because blob fees are now a distinct, independently-tracked market, block explorers and analytics dashboards have added dedicated views for blob-specific metrics — separate from the regular gas price you'd see for an ordinary transfer. Anyone curious about how cheap or expensive rollup activity currently is can check blob-specific fee trackers directly, rather than inferring L2 costs purely from mainnet gas prices, which no longer tell the whole story on their own now that the two markets move independently of each other.

Bottom line

EIP-4844 gave Ethereum a second, independently priced fee market specifically for the temporary data rollups need to post back to the base layer, replacing the previous approach of stuffing that data into expensive calldata. The result has been meaningfully cheaper layer 2 transactions, achieved without changing how regular gas fees work for anyone not directly posting blob data. It's a deliberate, incremental step toward a much larger scaling plan (full danksharding), not the final word on Ethereum's data availability roadmap.