Split the transaction into two charges

An ordinary Ethereum transaction pays execution gas. A blob-carrying transaction also pays for attaching data in blobs, a format commonly used by rollups. The sender can therefore face two costs for one transaction. Compare them separately when trying to explain a change from one batch to another.

Read the caps separately

Execution cost is based on gas used and the effective execution gas price, which can include a priority fee. The blob portion multiplies the blob gas used by the protocol’s blob base fee. The max_fee_per_blob_gas field is the sender’s price cap for the blob portion. Raising the execution priority fee does not reduce the blob base fee, and the blob fee itself has no separate priority tip.

Compare batches on a consistent basis

A block with a high execution base fee can have comparatively cheap blob space, and the reverse can occur. Record the number of blobs or total blob gas, the blob gas price, the execution gas used and its effective price. If comparing two rollup batches, also compare how much user data each batch carries. Cost per batch alone can conceal a change in compression or batching.

Keep data availability apart from contract storage

Blob data is made available through the consensus layer for a limited retention period. The EVM can work with references to blobs and proofs, while contracts do not directly read the blob contents as calldata. Use a data source appropriate to the retention window when verifying an old rollup batch.

Sources

  1. EIP-4844 · Shard Blob Transactions
  2. Ethereum.org · Gas and fees
  3. Ethereum.org · Transactions

Prepared with AI assistance. This guide explains protocol behavior for educational use.

Editorial policy (Chinese)