The practical guide to web3 domains for creators: what owning your name actually buys, what ENSv2 pricing looks like in 2026, and where the honest limits are.
Blobs are a new data type introduced in EIP-4844 (proto-danksharding) that allow layer-2 rollups to post transaction data on Ethereum at a fraction of the previous cost. Blobs are stored temporarily rather than permanently, dramatically reducing fees.
What Are Blobs
A blob (Binary Large Object) is a chunk of data attached to an Ethereum block that is not accessible by the EVM. Rollups use blobs to post compressed transaction data, which validators can still verify without permanently storing all the data.
Blob Properties
- Up to ~128 KB per blob
- Not executed or readable by smart contracts
- Stored for approximately 18 days then pruned
- Priced separately from regular gas (blob gas)
EIP-4844 and Proto-Danksharding
EIP-4844, activated in the Dencun upgrade (March 2024), introduced blobs as a stepping stone toward full danksharding.
Before Blobs
- Rollups posted data as calldata
- Calldata is stored permanently by all nodes
- High costs passed on to users
After Blobs
- Rollups post data as blobs
- Blobs are pruned after ~18 days
- Costs dropped 90% or more for L2 users
Blob vs Calldata
| Feature | Calldata | Blob |
|---|
| Storage | Permanent | Temporary (~18 days) |
| EVM Access | Readable | Not accessible |
| Cost | High | Much lower |
| Use Case | Smart contract calls | Rollup data posting |
Impact on Rollup Costs
Blobs reduced layer-2 transaction fees dramatically:
- Ethereum L2 transfers went from dollars to cents
- DeFi operations on L2s became competitive with centralized exchanges
- Enabled new use cases like microtransactions and gaming
Future Scaling
The current implementation supports up to 6 blobs per block. Full danksharding will increase this to 64 or more blobs, further scaling Ethereum's data capacity and driving L2 costs even lower over time.