Home / News / technologie

Layer 2 Rollup Economics: Blob Costs and Sequencer Revenue

NOUTITA NEWSROOM·15 OCT. 2026 À 20:01 (UTC+1)·6 MIN READ

PARALLEL EVM & ZK

TECHNOLOGIE

noutita.com#TECHNOLOGIE

In Brief (TL;DR)

An in-depth learning guide for U.S. readers exploring how EIP-4844 blob data space shapes data availability costs, blob pricing dynamics, and sequencer revenue in optimistic and zk-rollups. We balance theories with practical modeling steps and provide credible sources from GitHub, Etherscan, and L2Beat.

Layer 2 rollups sit atop Ethereum to scale throughput, but their economics hinge on a few moving parts: the price of posting data blobs to Ethereum (the EIP-4844 blob market), the data availability space these blobs occupy, and how sequencers (the entities that order and post L2 data to L1) recover costs and earn revenue. This guide dives into blob costs and sequencer revenue, offering a practical guide to think through the math, the competing viewpoints in the literature, and a hands-on workflow you can actually follow. We pull from primary sources—EIP-4844 specifications, Arbitrum/Optimism documentation, L2Beat data pages, and peer-reviewed arXiv papers—so you can ground your intuition in the work that drives real-world L2 economics. Citations appear inline so you can verify the facts directly.

Note: blob data markets and sequencer economics are an active area of research and product design. The numbers and models evolve as protocols experiment and as Ethereum’s data space dynamics change. Where possible, we anchor statements to primary sources and give you contrasting viewpoints to foster nuanced understanding.

In Brief (TL;DR)

EIP-4844 creates a dedicated blob data space in Ethereum blocks, with blob transactions and a separate blob data fee market. This shifts some data-availability costs away from standard L1 calldata into a cheaper, time-limited blob mechanism. See the EIP-4844 spec and GitHub documentation for the mechanics, including the idea that there is a blob base fee that is distinct from L1 gas and L2 execution costs. (eips.ethereum.org)

L2s like Arbitrum and Optimism post data blobs to Ethereum and recover costs through a mix of L1 blob fees, L2 execution fees, and revenue sharing. Arbitrum’s materials describe a Net Protocol Revenue construct that subtracts blob-related settlement costs from gross revenue, highlighting the data-posting cost as a key line item. Optimism emphasizes its revenue-sharing framework within the Superchain. (docs.arbitrum.foundation)

The blob market is intended to incentivize efficient data posting, with research suggesting blob sharing can lower DA costs for small rollups, but other work argues blob fees can remain a non-trivial cost driver for sequencers in the near term. This tension is a core theme in EIP-4844 economics literature. (arxiv.org)

Real-world metrics from L2Beat and on-chain data illustrate where blob usage stands today and how blob space is evolving relative to calldata. These sources are useful for tracing data availability costs and the scale of blob posting across L2s. (l2beat.com)

A concrete example from a live Ethereum transaction shows a blob-related datapath (Blob by EIP-4844) in action on a real transaction, underscoring the market’s practical dimension. (etherscan.io)

1. Theoretical Foundations & Invariants

Blob data space, three blobs per block, and a market that prices blob posting

EIP-4844 introduces a new blob-type transaction that carries data for rollups. The design separates blob data availability from the traditional calldata path and ties blob posting to a market mechanism that targets a capacity (commonly framed around a blob-per-block cadence). This separation is meant to reduce the data costs for rolling up transactions relative to posting all data as standard L1 calldata. The official GitHub spec describes the blob transaction type and the intention to enable a forward-compatible data availability model. (eips.ethereum.org)

The economics of blob posting revolve around a blob base fee that rollups pay (in addition to L1/Calldata costs) to post data. Researchers model this as a separate pricing tier that interacts with the traditional blocksize/data-packing decisions. Several technical references describe how blob pricing is intended to operate and what the target capacity implies for price dynamics. (arxiv.org)

Data availability space and the DA market structure

L2s rely on data availability sampling (DAS) and blob storage as the DA substrate for rollups. The blob space is a specialized, time-bound data channel that can be sampled for availability, and it is designed to be cheaper than full calldata posting while maintaining security guarantees through sampling. Ethereum.org’s data-availability pages summarize this paradigm and show how blobs fit into the broader data-availability strategy for rollups. (ethereum.org)

How blob costs feed into sequencer economics

For optimistic rollups such as Arbitrum, the protocol revenue model explicitly accounts for L1 blob posting (L1BaseFee) as part of the costs that must be covered by fees collected by users. The “AEP Fees Formula” and related Arbitrum documentation spell out the split: the blob posting cost is a primary line item that the sequencer must be reimbursed for, and the Net Protocol Revenue is the margin after settling those blob-related costs. This framing positions blob costs as a central determinant of sequencer profitability. (docs.arbitrum.foundation)

Competing viewpoints in the literature

A body of work argues that blob sharing and the fixed-capacity blob market can lower data-availability costs for smaller rollups, improving the overall economics of L2s. In contrast, other research points to the risk that blob costs may stay non-trivial for the near to medium term, especially as competition for blob space increases and as base revenue models evolve. These conversations are visible across arXiv papers and practitioner blogs, forming a two-sided debate about the trajectory of blob pricing and sequencer profitability. (arxiv.org)

The two-pronged reality: data costs can drop but sequencer costs can still be meaningful

The literature frequently juxtaposes a potential drop in data-availability costs thanks to blob space (and blob sharing) with the continuing importance of other cost factors such as data settlement and L1 gas, all of which shape sequencer margins. Practitioners emphasize that blob costs are a leading driver of sequencer profitability today, but there is a consensus that the market is still maturing and subject to shift as the ecosystem experiments with fee structures and revenue-sharing schemes. (forum.arbitrum.foundation)

Quote (illustrative): "Blob space posting is designed to be cheaper than traditional calldata, with a separate pricing mechanism that can adapt to demand while maintaining security via data availability sampling." This summarizes the core rationale behind EIP-4844 without locking in a single price path. (Source: EIP-4844 spec; GitHub mirror) (eips.ethereum.org)

Where the data sits today (metrics and optics)

L2Beat provides a data-availability snapshot for L2s and blob-related metrics. The blob data pages help observers track how blob usage and DA costs compare to traditional calldata usage, offering a practical lens on how blob economics translate into real-world costs and revenue opportunities for sequencers. Use these dashboards to sanity-check trends when building your own models. (l2beat.com)

Observational tensions in practice

Some researchers argue blob pricing can become self-stabilizing as multiple rollups compete for blob space, while others warn that early-stage data markets may exhibit volatility and misalignment between blob pricing and actual posting costs. The literature and practitioner discussions reflect this tension, and any modeling exercise should explicitly lay out the assumptions and sensitivities (e.g., capacity targets, demand curves, and settlement costs). (arxiv.org)

2. Step-by-Step Tutorial (Practice)

A. Prerequisites & Security

Core concepts you should know before attempting the practice

What is a Layer 2 rollup? Distinguish between optimistic and zk-rollups, and understand how data is posted to Ethereum via blobs under EIP-4844. See the EIP-4844 specification for the blob transaction type and the data-availability design. (eips.ethereum.org)

How blob pricing works in practice (blob base fee, capacity target, and the data market). See the discussions around blob pricing, data capacity targets, and their influence on stepwise pricing. (arxiv.org)

The way sequencers generate revenue today and how blob costs factor into margins. Arbitrum’s own docs describe the revenue calculus (gross revenue minus blob-related settlement costs), while Optimism explains the Superchain revenue split that feeds back to the ecosystem. (docs.arbitrum.foundation)

Security and risk notes

Blob pricing is not a one-shot forecast; it depends on demand, capacity, and protocol updates. Be mindful of evolving specs and governance proposals that can alter the pricing mechanism, the blob capacity target, or the revenue-sharing framework. (github.com)

Tools and data sources you should consult

Official specs and GitHub mirrors for EIP-4844 (EIPs repo) to ground definitions. (github.com)

Arbitrum and Optimism developer/docs for current fee-management rules and sequencer economics. (developer.arbitrum.io)

L2Beat data-availability dashboards to sanity-check blob usage trends. (l2beat.com)

Etherscan for on-chain blob-related transactions (for an example of blob posting in the wild). (etherscan.io)

B. Executing the Steps

Below is a practical, repeatable workflow you can run to build a disciplined blob-cost + sequencer-revenue model. The approach is intentionally modular so you can swap in new data sources as the market evolves.

Step 1: Establish the pricing primitives you will model

Identify the blob base fee per blob block (the core price to post a blob to a given block). This price is determined by the EIP-4844 blob market mechanism and capacity targets. For grounding, consult the EIP-4844 documentation and the GitHub mirrors that describe blob pricing. (eips.ethereum.org)

Clarify the per-transaction L1/calldata costs that still apply when a transaction is posted via L1 calldata (not blob). Some models separate these two cost streams: blob posting costs versus traditional L1 gas. Arbitrum’s AEP framework explicitly references L1BaseFee as the posting cost to settle on the parent chain. (docs.arbitrum.foundation)

Step 2: Quantify blob-space demand and capacity assumptions

Use L2Beat blob dashboards to gauge current blob usage, capacity, and DA costs across rollups. These numbers help calibrate demand curves for blob space and the implied price per blob under different market conditions. (l2beat.com)

Consider the target capacity logic in EIP-4844 (commonly discussed as a small, fixed number of blobs per block) and how this impacts price dynamics over time. The literature and the EIP describe the capacity-target framing that drives blob pricing. (eips.ethereum.org)

Step 3: Build a blob-cost per-block estimator

Compute blob costs per block as: number_of_blobs_per_block × blob_base_fee. If a given block targets three blobs, your per-block blob cost equals 3 × blob_base_fee. This simple relationship is central to many blob-market models and is explicitly discussed in the blob-fee discussions around EIP-4844. (eips.ethereum.org)

Step 4: Separate blob-posting costs from L2 execution costs

Blob fees are not the sole cost of running an L2 transaction. You must account for L2 execution costs (gas for executing transactions on the L2) and any other settlement costs that the sequencer bears when posting data to L1. Arbitrum’s AEP framework emphasizes the separation between blob posting costs and other revenue components. This separation matters for margin calculations. (docs.arbitrum.foundation)

Step 5: Model sequencer revenue given a revenue-sharing frame

Revenue can be framed as gross user fees collected by the L2 chain minus blob-related settlement costs, with additional revenue-sharing or governance-based allocations (as seen in Optimism’s Superchain model). The exact split informs the sequencer’s profitability and incentives to post data aggressively. See Optimism’s discussion of the Superchain revenue split and Arbitrum’s net-revenue framing for context. (optimism.io)

Step 6: Run two scenarios to illustrate editorial tension

Scenario A (Blob sharing improves economics): assume blob-competition-adjusted prices and effective DA-sharing reduce per-blob costs for small rollups. Use the “180 Days After EIP-4844” and related literature to justify the potential upside of blob-sharing dynamics. (arxiv.org)

Scenario B (Blob costs remain a meaningful cost driver): hold blob costs steady or rising with demand and competition, and show how even with blob space gains, the sequencer margin compresses if revenue grows slower than blob-posting costs. The Arbitrum sustainability discussions and practitioner analyses provide the empirical flavor for this viewpoint. (forum.arbitrum.foundation)

Step 7: Cross-check with live data and on-chain signals

If you have access to on-chain data tooling, verify a blob-transacting event through an Etherscan transaction page that references a blob posting. This helps connect your model to real-world activity and demonstrates the data path from user fee to blob posting to settlement. (etherscan.io)

Step 8: Document uncertainties and sensitivities

Clearly annotate your assumptions about blob-capacity targets, the shape of the blob-demand curve, and the revenue-sharing terms in play at broadcast time. The literature consistently notes that blob pricing dynamics depend on capacity targets, demand signals, and governance changes; be transparent about these dependencies in your model. (arxiv.org)

Concrete mini-example (illustrative, not a forecast)

Suppose a block posts three blobs, with blob_base_fee of X ETH per blob. The per-block blob cost is 3X. If the L2 chain collects Y ETH in transaction fees from users during that block, and Z ETH is spent to settle the blob data on L1, then the gross revenue is Y, the blob posting cost is 3X, and the net protocol revenue is roughly Y − 3X − Z (subject to governance allocations and any additional costs). This framing mirrors the cost-revenue accounting described in Arbitrum’s and Optimism’s materials. For the exact definition and governance treatment, see the cited sources. (docs.arbitrum.foundation)

What to watch for next

Blob-space capacity updates, new data-sharing patterns among rollups, and changes in revenue-sharing agreements can all swing sequencer margins. The research community continues to debate whether blob pricing will stabilize, soften, or re-price as the ecosystem matures. Keeping an eye on working papers and governance notes from Arbitrum and Optimism is a good practice if you’re building live models or investor-focused analyses. (arxiv.org)

Optional: where to find more granular data

L2Beat’s data-availability and blob pages are designed to help researchers track blob metrics and DA costs across rollups, and Arbitrum’s and Optimism’s own docs provide the governance and revenue-sharing context. Use these as reference points when you need to pull in updated figures. (l2beat.com)

A note on real-world signals

A live blob transaction on Ethereum has already been observed in on-chain data, illustrating the practical dimension of blob posting and its traceability via Etherscan. This is a reminder that blob markets are not abstract; they align with actual user flows and fees in the ecosystem. (etherscan.io)

Closing thought

The blob-based data market represents a fundamental redesign of how data availability costs are priced for rollups. The economics are still evolving, and the best practice for analysts and strategists is to model multiple plausible futures, anchored in the primary literature and followed by up-to-date dashboards like L2Beat and on-chain data. The literature is clear that blob economics will influence, and be influenced by, sequencer revenue, governance models, and the competitive dynamics across Optimism, Arbitrum, and emerging OP Stack ecosystems. (eips.ethereum.org)

Appendix: Key sources and pointers

EIP-4844 specification and blob-transaction concepts (GitHub mirrors and official pages) — for the mechanics and pricing rationale behind blobs. (github.com)

Data-availability, DAS, and blob-market framing (Ethereum.org and related literature) — for the DA paradigm and blob-market placement inside Ethereum’s data architecture. (ethereum.org)

L2Beat blob data and data-availability pages — for real-world metrics and dashboards to anchor assumptions. (l2beat.com)

Arbitrum and Optimism governance/docs on fees, revenue, and blob-POST costs — to ground the monetization logic in the actual protocol rules. (docs.arbitrum.foundation)

On-chain blob transaction example (Etherscan) — to illustrate the end-to-end data-path of blob posting. (etherscan.io)

Peer-reviewed and practitioner analyses on blob economics and capacity effects — for the two-sided debate on blob pricing and rollup economics. (arxiv.org)

Representative blog and RFC discussions about sequencer revenue and market dynamics — to show the broader market conversation. (forum.arbitrum.foundation)

Live governance and market-structure perspectives on Superchains and fee splits — to contextualize revenue-sharing implications in the ecosystem. (optimism.io)

If you’d like, I can tailor the tutorial to a specific L2 (e.g., Arbitrum vs. Optimism) or give you a ready-to-fill spreadsheet template with placeholder inputs for blob_base_fee, blobs_per_block, and gross-revenue assumptions so you can run quick sensitivity analyses. (All sources cited above.)