Skip to content

Blob (EIP-4844)

What a blob is under EIP-4844 (the Dencun upgrade, March 2024): a separate, temporary data lane for rollups with its own fee market, pruned from nodes after a few weeks.

A blob is a chunk of data — up to roughly 128 KB — that Ethereum began accepting on mainnet with EIP-4844, part of the Dencun upgrade activated in March 2024. Blobs exist for one purpose: giving rollups a cheap place to post the transaction data behind their batches, without that data competing for space in Ethereum’s regular gas market.

Two design choices make blobs cheap. First, they have their own fee market (“blob gas”), priced and adjusted independently of normal execution gas. Second, blobs are not stored permanently by Ethereum’s execution clients — nodes keep them for a limited retention window (on the order of a couple of weeks) and then prune them, on the assumption that anyone who needed the data to verify a rollup’s state has already had the chance to fetch and check it.

Why it matters

Before blobs, rollups posted their data as regular transaction call data, paying full L1 gas rates for bytes that didn’t need to live on Ethereum forever. Blobs decoupled “data that needs to be available briefly so anyone can verify it” from “state that needs to live on Ethereum permanently” — the core idea behind data availability for rollups, and a direct driver of lower L2 transaction fees.

Example

An optimistic rollup batches a few thousand user transactions, then posts the compressed data for that batch into one or more blobs on L1, alongside a much smaller on-chain commitment that lets anyone later reconstruct and check the batch.

Related · Protocol

← All glossary terms

Not financial advice.