The short answer: most Layer 2 users in 2026 do not pay an Ethereum blob fee directly. They pay a transaction fee to the Layer 2. That fee usually reflects several underlying costs: executing the transaction on the L2, publishing enough data to Ethereum for data availability, and any chain-specific operator or protocol charges. Blob fees matter because they influence the data-availability portion of many rollup fees, while ordinary gas fees still price computation and state changes in a separate market.
This distinction matters because “Ethereum gas is cheap” and “blob fees are cheap” are not the same statement. A rollup can face low blob costs while its own execution demand is high, or the reverse. The final fee shown by a wallet depends on the L2's fee formula, transaction type, congestion, compression, and how the chain passes infrastructure costs through to users.
Ethereum introduced blob-carrying transactions with EIP-4844. A blob is temporary data intended primarily for rollups. Blob data is not ordinary EVM calldata and is priced with its own unit, blob gas. The EIP-4844 specification explicitly defines blob gas as independent from normal execution gas and gives it a separate base-fee mechanism.
Normal Ethereum gas still prices execution on Layer 1: running EVM operations, touching storage, and processing regular transaction data. Blob gas prices the special data-availability capacity used by blob-carrying transactions. Ethereum exposes the current blob base fee separately from the ordinary base fee; the Ethereum opcode reference documents both BASEFEE and BLOBBASEFEE.
| Cost | What it prices | Who usually pays it directly | What an L2 user sees |
|---|---|---|---|
| Ethereum execution gas | L1 computation and state changes | The sender of an L1 transaction | Usually only indirectly, when the rollup has L1 settlement or verification costs |
| Ethereum blob fee | Temporary blob data availability | The rollup batch submitter sending the blob transaction | Usually an embedded data-availability component of the L2 fee |
| L2 execution fee | Computation and state changes on the L2 | The L2 user | Part of the transaction fee shown by the wallet |
| Operator/protocol fee | Chain-specific overhead, proving, sequencing, or configured charges | The L2 user when the chain includes it | May be folded into the total or exposed separately by tooling |
The important 2026 change is not that blobs replaced gas. They did not. The change is that Ethereum increased the amount of blob data the network can safely carry.
Fusaka went live on December 3, 2025 and introduced PeerDAS, which lets nodes sample portions of blob data instead of requiring every node to download every blob in full. Ethereum's PeerDAS documentation explains that this architecture is designed to expand data-availability capacity while limiting per-node bandwidth requirements.
Ethereum then used Blob-Parameter-Only, or BPO, forks to raise capacity without bundling the change into another large protocol upgrade. As of September 29, 2026, the latest finalized mainnet parameters documented in the canonical BPO2 record are a target of 14 blobs per block and a maximum of 21. BPO2 activated on January 7, 2026. See EIP-8135 and the Ethereum Foundation's January 2026 protocol checkpoint.
A draft BPO3 document exists, but as of this date it does not contain finalized activation parameters. That means readers should not assume a higher mainnet target simply because Ethereum's architecture can support more capacity. The draft status is visible in EIP-8138.
For a typical rollup transaction, a useful mental model is:
Total L2 fee ≈ L2 execution cost + L1 data-availability cost + chain-specific overhead.
That is a model, not a universal formula. Different rollups calculate and allocate these pieces differently.
Your swap, transfer, mint, contract call, or account-abstraction operation still consumes resources on the Layer 2. A simple ETH transfer normally uses fewer L2 execution resources than a complicated DeFi transaction. This portion can rise even when Ethereum blob fees are near their minimum if the L2 itself is congested or the transaction performs expensive computation.
A rollup must make enough information available so that its state can be independently reconstructed or verified according to its design. For many Ethereum rollups, that means publishing compressed transaction or state data to Ethereum blobs. The batch submitter pays the blob fee on L1, then the rollup's fee mechanism allocates or estimates that cost across L2 transactions.
The OP Stack provides a concrete example. Its official execution-engine specification says the L1-cost fee is added to the L2 execution fee and, after the Ecotone upgrade, incorporates both the Ethereum L1 base fee and the L1 blob base fee through configured scalars. This is why the number shown to an OP Stack user is not simply “blob fee times transaction size.” Compression and chain parameters matter.
Some chains add explicit or implicit charges for operating the network, proving, or other services. OP Stack's Isthmus specification, for example, added an operator fee that can be configured alongside the standard L2 gas fee and L1 data fee. Other rollup architectures account for costs differently.
ZKsync illustrates another model. Its official fee-model documentation explains that users pay for L2 computation while the system also accounts for “pubdata,” the public data needed on Ethereum. ZKsync is state-diff based, so the amount of pubdata can depend more on the state changes a transaction creates than on the raw size of the original transaction.
Consider two transactions submitted while Ethereum's blob base fee is unchanged.
Transaction B can cost more because its L2 execution component is larger, its data footprint may be larger after compression, or both. The blob fee is only the market price for Ethereum's blob capacity; it is not a flat per-user toll.
The reverse can also happen. Suppose the L2 is quiet, but blob demand across Ethereum rises because many rollups are posting data at once. The data-availability portion of fees can rise even if execution on your chosen L2 has not become more computationally expensive.
Blob fees are especially relevant when you are making many low-computation transactions whose cost is dominated by publishing data, or when you are comparing rollups that settle to Ethereum but use different compression and pricing policies. They also matter to applications such as payments, social transactions, gaming actions, and other high-throughput workloads where per-transaction data overhead can be a significant fraction of the total fee.
Blob fees matter less as a direct user-facing concept when the transaction's dominant cost is execution, when the chain subsidizes data costs, when a wallet abstracts fees through sponsorship, or when the network uses a different data-availability design. In those situations, checking only Ethereum's blob base fee can give a misleading picture of what the wallet will charge.
Start with the fee quote in the wallet or dapp, because that is the amount relevant to your transaction. Then, if the fee is unexpectedly high, check which component moved.
No. Blobs added a separate data-availability fee market. Ethereum execution gas still exists, and L2s still have their own execution pricing.
No. The L2 still has execution costs and may have operator or protocol charges. Complex contract interactions can remain materially more expensive than simple transfers.
Usually not. The L2 user submits an ordinary transaction to the rollup. The rollup's batcher or operator later packages many transactions and posts data to Ethereum, often using blobs.
It increases data-availability supply and can reduce pressure on the data component, but it does not guarantee a particular user fee. Demand, L2 execution load, compression, configured scalars, proving costs, subsidies, and operator policies still matter.
When you use an Ethereum Layer 2 in 2026, think of the wallet fee as a bundled price rather than a single Ethereum gas number. Blob fees price the rollup's access to Ethereum data availability. Gas fees price execution. Your L2 combines those economics with its own rules and infrastructure costs.
The most useful question is therefore not “What is the Ethereum blob fee right now?” but “Which part of this Layer 2 transaction is driving my quoted fee?” For a simple transfer, data availability may be a meaningful share. For a complex contract call, L2 execution may dominate. For a chain with an explicit operator fee, there may be a third visible component.
That framing remains accurate even as Ethereum continues scaling blobs: blob capacity can grow, and blob prices can fall, without eliminating execution gas or making every rollup transaction equally cheap.
A successful blockchain transaction does not always mean a wallet will display the tokens. Learn how to verify the network, recipient, token contract, explorer balance, bridge status, and exchange deposit details safely.
Why liquid staking tokens can trade below redemption value, how withdrawal queues, liquidity, risk and time affect the discount, and when swapping or redeeming may make more sense.
Use this practical airdrop safety checklist to verify official claim contracts, inspect wallet permissions, spot malicious signatures, and respond to suspicious approvals.
Learn how to monitor validator performance and commission changes from primary blockchain data, compare the trade-offs, and build a reliable delegator check routine.
Learn how to match crypto transfers across exchange and wallet exports, preserve cost basis, separate fees, and review Form 1099-DA before calculating gains.
Learn how MEV protection works for retail DEX swaps, how private transactions reduce sandwich risk, how slippage affects exposure, and what trade-offs to check before you trade.
Understand how account abstraction wallets use session keys, paymasters, and recovery rules, plus the permissions and risks to check before signing.
Avoid crypto withdrawal mistakes by checking the receiving chain, token contract, address, and memo or destination tag before you send funds.
Before delegating restaked assets, verify an operator’s AVS exposure, slash conditions, loss limits, redistribution rules, and exit delays with this practical checklist.
Learn what crypto proof of reserves can verify, what liabilities it may omit, and how to check an exchange’s snapshot, customer balances, and audit scope.
