Ethereum Blob Fees Explained: How Proto-Danksharding Changes L2 Costs
Ethereum Blob Fees: What Are They?
Ethereum Blob Fees are the fees paid for including temporary data blobs in Ethereum transactions. They were introduced through EIP-4844, also known as Proto-Danksharding, as part of the Dencun upgrade in March 2024.
Blobs provide Layer 2 rollups with a dedicated way to publish transaction data to Ethereum without using the traditional calldata pricing model. Ethereum’s official EIP-4844 specification describes blob gas as a separate fee market with its own base fee.
This distinction matters because Ethereum has two different resource markets involved in these transactions:
- Regular execution gas
- Blob gas
The price of one does not directly determine the price of the other.
For Layer 2 users, this creates a potentially important cost-saving mechanism because rollups can batch transactions and publish compressed data through blobs.
What Is Proto-Danksharding?
Proto-Danksharding is the first major stage of Ethereum’s longer-term danksharding roadmap.
Ethereum’s Danksharding roadmap explains that Proto-Danksharding adds data blobs to Ethereum blocks, giving rollups a cheaper way to publish data.
The term can sound complicated, but the basic idea is relatively straightforward.
A Layer 2 processes many transactions away from Ethereum Mainnet. It then needs to publish sufficient information back to Ethereum so that the rollup’s state can be independently verified.
Before blobs, rollups relied heavily on calldata for this data publication.
With EIP-4844, rollups can use dedicated blob space instead.
This does not mean blobs are permanent storage. Ethereum documentation states that blobs are intended to remain available for roughly 18 days, after which they can be pruned from ordinary clients. Long-term archival availability is a separate concern.
How Ethereum Blob Fees Work
The blob fee market is similar in concept to Ethereum’s EIP-1559 execution-fee market, but it operates separately.
EIP-4844 introduced:
- Blob gas
- A blob base fee
- A target amount of blob space
- A maximum amount of blob space
- An excess blob gas value used to adjust pricing
The protocol calculates the blob base fee according to blob-space demand.
When blob usage exceeds the target, excess blob gas accumulates and the blob base fee can rise.
When demand is lower, the fee can move downward.
The Ethereum EIP-4844 specification defines this adjustment mechanism and the formula used to calculate the blob base fee.
This means Ethereum Blob Fees are driven primarily by demand for blob space rather than by the computational complexity of ordinary smart-contract execution.
Ethereum Blob Fees vs Normal Gas Fees
One of the easiest mistakes is treating blob fees and normal Ethereum gas fees as the same thing.
They are not.
A normal Ethereum execution fee is associated with computation and other execution-layer resources.
A blob fee is associated with data availability space.
A rollup transaction can therefore be affected by both.
Ethereum’s gas and fees documentation explains how normal gas measures computational work, while its transaction documentation describes blob-carrying transactions as a separate transaction type.
This separation allows the blob market to respond specifically to demand for Layer 2 data availability.
How Ethereum Blob Fees Affect L2 Costs
Layer 2 users typically do not pay the raw Ethereum blob fee as a separate line item.
Instead, rollup operators incur costs for publishing data to Ethereum and generally incorporate those costs into the L2 fee structure.
For optimistic rollups, Ethereum identifies several components of user fees, including L1 data publication, blob gas, and L2 operator costs. Ethereum’s optimistic-rollup documentation explains how these components work together.
For ZK-rollups, fees can also include data publication, L2 operator costs, and proof-related expenses. Ethereum’s ZK-rollup documentation describes these components.
This means lower Ethereum Blob Fees can reduce one important cost faced by rollups, but they do not automatically make every L2 transaction free or equally cheap.
Why Blobs Are Cheaper Than Calldata
Calldata and blobs both allow rollups to publish information to Ethereum, but they have different pricing and storage characteristics.
Calldata remains part of Ethereum’s permanent historical data and is priced through regular execution gas.
Blobs are temporary data objects with a dedicated fee market.
Ethereum’s documentation explains that blobs were designed specifically for rollup data and are generally cheaper than calldata for this use case. The data remains available during the protocol’s required serving window, while longer-term access can be handled by archival systems.
The difference is therefore not simply that blobs are “cheap storage.”
They are better understood as temporary data availability infrastructure designed for rollups.
Ethereum Blob Fees and Data Availability
Data availability is essential to rollup security.
A rollup publishes data to Ethereum so independent participants can reconstruct and verify the rollup’s state.
Ethereum’s data availability documentation explains why publishing rollup data is necessary for permissionless verification.
This is one reason blob fees matter beyond simple transaction pricing.
The goal is not merely to reduce costs. Ethereum needs a scalable way for rollups to make relevant data available without overwhelming node operators.
Proto-Danksharding therefore attempts to balance:
- Rollup data availability
- Network capacity
- Node-resource requirements
- L2 affordability
- Ethereum security
Ethereum Blob Fees and Blob Capacity in 2026
The blob system has expanded significantly since EIP-4844 first launched.
The original Dencun configuration targeted 3 blobs per block and allowed a maximum of 6 blobs.
Ethereum later increased these limits through subsequent upgrades.
Following Fusaka and its Blob Parameter Only upgrades, Ethereum reached a target of 14 blobs per block and a maximum of 21 blobs per block in January 2026.
Ethereum’s January 2026 protocol checkpoint described this as a 2.3× increase in L2 data space compared with the pre-Fusaka configuration. The canonical BPO2 specification records the 14-target and 21-maximum configuration.
This is important for L2 economics because more available blob space can reduce the likelihood that rollups compete for a severely constrained data-availability resource.
However, greater capacity does not guarantee permanently low blob fees.
If demand increases faster than capacity, blob prices can rise again.
Current 2026 Ethereum Blob Fee Conditions
A recent Blobscan Ethereum Mainnet snapshot shows blob gas pricing at only a few million wei per blob gas unit, equivalent to roughly 0.005 Gwei per blob gas in the snapshot reviewed for this article.
The same snapshot showed approximately 22 million blobs, around 4.5 million blocks, and about 2.67 TiB of total blob data size recorded on Ethereum Mainnet.
These figures change continuously, so they should be treated as a point-in-time snapshot rather than a permanent average.
They also illustrate an important feature of the blob market: prices can remain low when available blob capacity comfortably exceeds current demand.
A June 2026 Blobscan block example showed a blob gas price of approximately 0.011 Gwei, again indicating how low blob pricing can become during periods of relatively modest demand.
For live conditions, readers should use a current blob explorer rather than relying on a historical article snapshot.
Why Low Ethereum Blob Fees Do Not Guarantee Cheap L2 Transactions
It is tempting to conclude that low blob fees automatically mean extremely cheap L2 transactions.
The relationship is more complicated.
An L2 transaction can include several cost components:
- L1 data publication
- L2 execution
- L2 operator fees
- Proof generation
- Proof verification
- Sequencer-related costs
- Network-specific overhead
For example, ZK-rollups may have additional proof-generation and verification costs that do not appear in the blob market itself.
Transaction complexity also differs between applications.
A simple token transfer may require less data than a more complex DeFi interaction.
Therefore, Ethereum Blob Fees are an important variable, but they are only one component of the final amount a user pays.
Ethereum Blob Fees and Rollup Compression
Compression is another major part of L2 fee economics.
Rollups do not necessarily publish every transaction in the same raw format used by users.
Instead, transaction data can be compressed and batched so that one Ethereum publication covers many L2 transactions.
This spreads the cost of posting data across a larger number of users.
Ethereum’s Layer 2 scaling documentation explains how rollups batch transactions and publish data to Ethereum to reduce per-transaction costs.
This is why changes in blob pricing can have different effects across rollups.
An L2 with efficient compression and large batches may respond differently from an L2 with higher data requirements.
Ethereum Blob Fees and Rollup Competition
A larger blob market can influence competition between Layer 2 networks.
When data availability is scarce and expensive, rollups face greater costs for posting batches.
As blob capacity increases, that constraint can become less severe.
This can give rollups more room to scale transaction throughput without paying the same data-publication cost.
Ethereum’s 2026 protocol roadmap continues to prioritize additional blob scaling. The Ethereum Foundation’s 2026 protocol priorities update states that further blob-parameter increases remain part of the broader scaling work.
This suggests the blob market is still an evolving component of Ethereum’s scaling architecture rather than a finished design.
Ethereum Blob Fees and Full Danksharding
Proto-Danksharding is not the final destination.
Ethereum’s longer-term danksharding roadmap aims to expand data availability substantially while using data-availability sampling.
The Ethereum Danksharding roadmap explains that later stages are designed to allow validators to verify blob availability through sampling rather than requiring every node to process the entire data set in the same way.
The objective is greater data capacity while preserving Ethereum’s security and decentralization properties.
Proto-Danksharding therefore provides the current infrastructure and fee market from which future scaling improvements can evolve.
How Traders and Developers Should Think About Ethereum Blob Fees
For developers building on L2s, blob economics can influence transaction costs, batching strategies, and application design.
For users, the main point is simpler:
L2 fees are not determined by Ethereum Mainnet gas alone.
Blob demand is another important variable.
When blob fees are low, rollups may face lower L1 data-publication costs. When demand rises and blob space becomes more competitive, those costs can increase.
A useful way to understand the market is to track:
- Blob base fee
- Blob utilization
- Target vs maximum blob count
- L2 transaction fees
- Data-compression efficiency
- Rollup activity
- Ethereum execution fees
Readers following broader Ethereum developments can also explore Coin Network’s Ethereum section and its DeFi coverage for related network and market developments.
Common Misunderstandings About Ethereum Blob Fees
Blob Fees Are the Same as ETH Gas Fees
They are separate pricing mechanisms, even though both are measured through gas-like units.
Blobs Are Permanent Ethereum Storage
They are temporary data-availability objects rather than permanent archival storage.
Low Blob Fees Mean Every L2 Transaction Is Cheap
L2 fees include other components beyond blob publication.
More Blobs Always Mean Lower Fees
More capacity can reduce scarcity, but demand can increase at the same time.
Proto-Danksharding Is Full Danksharding-
Proto-Danksharding is an intermediate stage of Ethereum’s broader data-availability scaling roadmap.
Ethereum Blob Fees: Practical Checklist
When evaluating L2 cost trends, check:
- Blob base fee: What is the current blob price?
- Utilization: Is blob capacity heavily used?
- Target: How many blobs does Ethereum currently target?
- Maximum: What is the per-block maximum?
- L2 data usage: How much data does the rollup publish?
- Compression: How efficiently does the L2 batch transactions?
- Execution fees: What does the L2 charge for computation?
- Proof costs: Are proof-generation or verification expenses significant?
- Network activity: Is L2 demand rising?
- Capacity roadmap: Are additional blob increases planned?
For additional educational material, Coin Network’s Cryptopedia archive provides broader blockchain explainers.
Conclusion
Ethereum Blob Fees are a separate pricing mechanism for the temporary data space introduced by Proto-Danksharding.
EIP-4844 gave Layer 2 rollups a dedicated way to publish data to Ethereum, reducing reliance on more expensive calldata for rollup data.
Since its introduction, Ethereum has expanded blob capacity. By January 2026, the network had reached a 14-blob target and 21-blob maximum per block, providing substantially more L2 data capacity than the original Dencun configuration.
Current 2026 blob-market snapshots also show periods of very low blob pricing, although the fee can change as demand changes.
The most important takeaway is that blob fees should be viewed as one component of L2 economics, not as the entire transaction fee.
Rollup execution, data compression, operator costs, proof-related expenses, and Ethereum’s broader data-availability capacity all influence what users ultimately pay.
Proto-Danksharding therefore represents not simply a fee reduction, but a change in how Ethereum prices and supplies the data-availability resource needed for rollup scaling.
FAQs
1. What are Ethereum Blob Fees?
Ethereum Blob Fees are fees charged for using Ethereum’s temporary blob data space.
They operate through a separate blob-gas market introduced by EIP-4844.
2. What is Proto-Danksharding-Ethereum Blob Fees?
Proto-Danksharding is the first stage of Ethereum’s danksharding roadmap.
It introduced blobs through EIP-4844 to provide rollups with cheaper data availability.
3. Why were blobs introduced-Ethereum Blob Fees?
Blobs were introduced to give Layer 2 rollups a more efficient way to publish transaction data to Ethereum.
This can reduce an important component of L2 data-publication costs.
4. Are blob fees the same as Ethereum gas fees?
No.
Blob gas and normal execution gas use separate pricing mechanisms.
A transaction involving blobs can therefore have both execution-related and blob-related costs.
5. How are Ethereum Blob Fees calculated?
Blob fees depend on the amount of blob gas used and the current blob base fee.
The EIP-4844 specification defines the calculation and dynamic adjustment mechanism.
6. How many blobs can Ethereum currently include?
Following BPO2 in January 2026, Ethereum’s mainnet blob target is 14 blobs per block and the maximum is 21 blobs per block.
The BPO2 specification records these current protocol parameters.
7. Are blobs permanent?
No.
Ethereum requires blob data to remain available for a limited serving period of roughly 18 days. Blobs are not designed to replace permanent archival storage.
8. Do lower blob fees automatically reduce L2 transaction fees?
They can reduce an L2’s data-publication costs, but the final user fee also depends on execution, operator charges, compression, proof costs, and other factors.
9. Do ZK-rollups use blobs?
Yes.
Ethereum’s ZK-rollup documentation explains that ZK-rollups can publish data using blobs or calldata.
10. Do optimistic rollups use blobs?
Yes.
Optimistic rollups can publish compressed transaction data through blobs, reducing their dependence on calldata for data publication.
Ethereum’s optimistic-rollup documentation explains how blob gas fits into their fee structure.
11. What happens when blob demand increases?
When blob usage exceeds the target, the blob base fee can increase through Ethereum’s dynamic pricing mechanism.
This makes blob space more expensive until demand and supply conditions change.
12. Where can I track Ethereum Blob Fees?
Live blob conditions can be monitored through Blobscan’s Ethereum Mainnet explorer, while protocol parameters can be checked against the official Ethereum EIP-4844 specification.
For broader Ethereum and DeFi developments, Coin Network’s Ethereum coverage and DeFi section provide additional context.
