After about 18 days, Ethereum nodes are allowed to delete, or prune, the actual data stored inside a blob. The blob itself does not remain permanently available from ordinary Ethereum nodes.
However, this does not mean that the entire blob transaction disappears from the blockchain. The transaction and the cryptographic information associated with the blob remain part of Ethereum’s blockchain history.
In simple terms:
The blob data can be pruned after about 18 days, but the blockchain record referencing the blob remains.
This temporary design was introduced with EIP-4844, also known as Proto-Danksharding, to make Ethereum Layer 2 data availability cheaper and more scalable.
What Are Ethereum Blobs?
Ethereum blobs are temporary data containers introduced as part of Ethereum’s Dencun upgrade through EIP-4844.
They were primarily designed to help Layer 2 rollups publish large amounts of transaction data to Ethereum without putting all of that information into traditional calldata.
Blobs provide a separate data-availability mechanism with their own fee market called blob gas.
Unlike traditional calldata, blob data is not intended to become permanent blockchain history.
How Long Are Ethereum Blobs Stored?
Ethereum’s protocol defines a minimum blob data retention period of 4,096 epochs.
With Ethereum’s normal 12-second slot timing, this is approximately 18.2 days.
For simplicity, this is commonly described as about 18 days.
The important point is that 18 days is a minimum retention period for blob data on Ethereum nodes, not a guarantee that every copy of the data disappears exactly at the 18-day mark.
What Happens to Ethereum Blobs After 18 Days?
After the required retention period has passed, Ethereum nodes can prune the actual blob contents.
The process can be understood in three parts:
1. The Blob Becomes Eligible for Pruning
Once the blob reaches the protocol-defined retention period, nodes no longer need to keep its contents available.
2. Nodes Can Delete the Blob Contents
Individual Ethereum nodes can remove the actual blob data from their local storage.
This helps control the amount of disk space required to operate an Ethereum node.
3. The Blockchain Record Remains
The associated transaction and cryptographic commitment remain part of Ethereum’s blockchain history.
Therefore, pruning the blob data does not mean that the transaction itself is removed from Ethereum.
Does Ethereum Delete the Blob Transaction After 18 Days?
No.
This is an important distinction.
Ethereum can prune the blob data, but the transaction that carried the blob remains part of the blockchain.
Think of it like this:
Blob contents → temporary
Blob transaction → persistent blockchain history
Blob commitment → remains associated with the transaction
So, the expiration of the blob’s availability period does not reverse or remove the original transaction.
Can You Still Find the Blob Transaction After 18 Days?
Yes.
You can still find the transaction and its associated blockchain information after the blob data has become eligible for pruning.
However, finding the transaction does not necessarily mean that you can retrieve the complete original blob contents from a normal Ethereum node.
This distinction is important when examining old blob transactions.
Can You Recover an Old Blob After 18 Days?
Not necessarily from a standard Ethereum node.
Once the retention period has passed, a node may have already pruned the blob contents.
However, other participants may have retained their own copies.
For example, historical blob data may be preserved by:
- Layer 2 operators
- Specialized archival infrastructure
- Data-availability services
- Independent Ethereum infrastructure providers
Therefore, an old blob may still exist somewhere even though ordinary Ethereum nodes are no longer required to retain it.
Does Blob Data Get Deleted Everywhere After 18 Days?
No.
The 18-day period should not be interpreted as a global deletion deadline.
It is a protocol-level retention requirement for Ethereum’s blob data.
Different entities can choose to keep copies for longer.
For example, a rollup operator may retain historical data because it can be useful for reconstructing or auditing Layer 2 history.
So:
Ethereum nodes can prune old blobs, but anyone who independently stored a copy can keep that data for much longer.
Why Does Ethereum Prune Blobs?
The primary reason is scalability.
Ethereum wants to provide inexpensive data availability for Layer 2 networks without requiring every Ethereum node to store an ever-growing amount of blob data forever.
If blobs were permanent, the amount of data that Ethereum nodes would need to store could grow significantly over time.
Temporary blob storage creates a compromise:
Short-term data availability + lower long-term storage requirements
This is an important part of Ethereum’s scaling architecture.
Why Do Layer 2 Rollups Use Blobs?
Layer 2 rollups process transactions away from Ethereum’s main execution layer.
They still need to publish relevant data to Ethereum so that the information needed to verify the rollup remains available.
Before EIP-4844, rollups relied heavily on calldata for this purpose.
EIP-4844 introduced blobs as a more efficient data-availability mechanism.
A simplified flow is:
Users
↓
Layer 2 rollup
↓
Transactions are batched
↓
Data is published through blobs
↓
Ethereum provides temporary data availability
↓
Blob data eventually becomes eligible for pruning
This design helps reduce the cost of scaling transactions through Layer 2 networks.
What Happens to the Blob Hash After 18 Days?
The cryptographic information associated with the blob does not simply disappear when the blob contents become eligible for pruning.
A blob transaction contains a versioned hash associated with the blob.
This allows the blockchain to maintain a cryptographic reference to the blob even after the actual blob contents may no longer be available from ordinary nodes.
This creates an important distinction:
Hash/commitment → remains
Actual blob contents → can be pruned
Can Smart Contracts Read Blobs After 18 Days?
Smart contracts cannot directly read the complete contents of blobs during EVM execution in the first place.
Blobs are designed primarily for data availability, not as permanent smart contract storage.
After the blob becomes eligible for pruning, the actual data becomes even less likely to be retrievable from standard Ethereum nodes.
Smart contracts can work with information associated with blobs, such as their versioned hashes, but this should not be confused with directly reading the blob contents.
What Happens If a Layer 2 Needs an Old Blob?
Layer 2 systems generally need to maintain access to historical information beyond Ethereum’s blob retention period.
This is why rollup infrastructure and other specialized systems can preserve historical data independently.
The key idea is:
Ethereum does not have to store every blob forever for the historical information to remain recoverable somewhere.
The ecosystem can maintain additional copies when long-term access is necessary.
Ethereum Blobs vs Calldata After 18 Days
The difference becomes especially clear when comparing blobs with calldata.
| Feature | Ethereum Blobs | Ethereum Calldata |
|---|---|---|
| Retention | Temporary | Persistent transaction history |
| ~18-day pruning | Yes | No equivalent blob-style expiry |
| Main purpose | Layer 2 data availability | Transaction and smart contract input |
| Fee market | Blob gas | Regular gas |
| Smart contract access | Cannot directly read blob contents | Can read calldata |
| Permanent blockchain history | Blob contents are not permanent | Calldata is part of transaction history |
This temporary nature is one of the main reasons blobs can provide a more scalable data-availability mechanism for rollups.
Is an Ethereum Blob Lost Forever After 18 Days?
Not necessarily.
After approximately 18 days, an ordinary Ethereum node may have pruned the blob.
But if another participant stored a copy, the data can still exist outside that node.
Therefore, there are two separate questions:
Is the blob still required to be stored by Ethereum nodes?
No, after the retention period.
Can a copy of the blob still exist somewhere?
Yes.
This distinction is important when discussing Ethereum blob expiration.
Does Blob Expiration Affect Layer 2 Transactions?
The expiration of blob data does not mean that Layer 2 transactions are automatically reversed, deleted, or invalidated.
The blob’s purpose is to provide data availability during the relevant period.
Afterward, the actual blob contents can be pruned according to Ethereum’s storage rules.
The Layer 2’s historical state and transaction records can still be maintained by the rollup and its infrastructure.
Frequently Asked Questions
What happens to Ethereum blobs after 18 days?
After the protocol-defined retention period of roughly 18 days, Ethereum nodes can prune the actual blob contents. The associated transaction and cryptographic commitment remain part of Ethereum’s blockchain history.
Are Ethereum blobs deleted after exactly 18 days?
Not necessarily. About 18 days is the minimum retention period. Nodes can prune eligible blob data afterward, so deletion does not necessarily occur at one exact moment.
Does the blob transaction disappear after 18 days?
No. The transaction remains part of Ethereum’s blockchain history even though the actual blob contents can be pruned.
Can you access an Ethereum blob after 18 days?
A normal Ethereum node may no longer have the blob contents after the retention period. However, specialized services, rollup operators, or other participants may have retained copies.
Are Ethereum blobs permanent?
No. Blob contents are temporary. They are designed to remain available for a limited period rather than becoming permanent blockchain data.
Why are Ethereum blobs temporary?
Blobs are temporary to provide Layer 2 rollups with affordable data availability while limiting the long-term storage burden placed on Ethereum nodes.
What remains after an Ethereum blob is pruned?
The transaction containing the blob and its associated cryptographic information remain part of Ethereum’s blockchain history. The actual blob contents may no longer be available from the node that pruned them.
Can Layer 2 rollups keep blobs longer than 18 days?
Yes. The approximately 18-day period applies to the protocol’s blob data retention requirement. Rollup operators and other infrastructure can independently preserve copies for longer.
What is the difference between blob expiration and transaction expiration?
A blob’s data can become eligible for pruning, but the Ethereum transaction that references the blob does not expire or disappear. The transaction remains part of the blockchain.
Final Answer
After about 18 days, Ethereum blobs become eligible for pruning. Ethereum nodes can delete the actual blob contents from their local storage, reducing the long-term storage requirements of the network.
But the blob transaction does not disappear.
The easiest way to remember it is:
The blob data expires; the blockchain transaction does not.
And because other infrastructure can independently retain copies, an old blob may still be available from specialized data providers or Layer 2 systems even after ordinary Ethereum nodes have pruned it.
This temporary data model is a key part of EIP-4844 and Ethereum’s strategy for scaling Layer 2 rollups while controlling blockchain storage growth.
