Blob Gas

Overview

Blob gas measures the data capacity consumed by blob-carrying transactions introduced for Ethereum’s rollup-focused scaling. Each blob represents a fixed amount of blob gas, and the protocol tracks blob demand separately from ordinary execution gas.

The blob base fee changes according to recent blob usage and is paid in addition to the execution gas needed for the transaction envelope and any contract calls. Blob data is temporarily available to the network but is not directly readable by EVM contracts; contracts can access commitments instead. Rollup operators should estimate both blob and execution fee components, set appropriate maximums, and monitor inclusion conditions. Accounting systems must separate blob fees from regular gas charges. Low execution congestion does not guarantee cheap blobspace when many rollups compete for the same data capacity.

A pending quote can change before inclusion, and a transaction that fails at execution may still consume a network fee. Payment systems should store the canonical transaction identifier, inclusion block, execution result, consumed resources, and effective fee reported by the final receipt. Operational policies should be tested against low-demand, congested, replaced, reverted, and reorganized transactions. Monitoring should distinguish a pricing error from delayed inclusion or failed execution, since each condition requires a different customer message and recovery action. Wallet defaults, quoted caps, and minimum protocol charges are different values, so interfaces should label each field and avoid presenting a maximum authorization as the amount ultimately paid. An estimate should identify the fee unit, network, block context, and transaction parameters used to calculate it.