Skip to content

Commit 3349bfa

Browse files
iankressinwackerow
andauthored
refactor: intro term blob and punctuation/capitalization
Co-authored-by: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
1 parent 2038620 commit 3349bfa

File tree

1 file changed

+1
-1
lines changed
  • public/content/developers/docs/scaling/optimistic-rollups

1 file changed

+1
-1
lines changed

public/content/developers/docs/scaling/optimistic-rollups/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -198,7 +198,7 @@ Finally, we should note that L2 > L1 message calls between contracts need to acc
198198

199199
Optimistic rollups use a gas fee scheme, much like Ethereum, to denote how much users pay per transaction. Fees charged on optimistic rollups depends on the following components:
200200

201-
1. **State write**: Optimistic rollups publish transaction data and block headers (consisting of the previous block header hash, state root, batch root) to Ethereum as `blobs`. [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844) introduced a cost-effective solution for including data on-chain. `blobs` is a new transaction field that allows rollups to post compressed state transition data to Ethereum L1 Unlike `calldata`, which remains permanently on-chain, blobs are short-lived and can be pruned from clients after [4096 epochs](https://github.com/ethereum/consensus-specs/blob/81f3ea8322aff6b9fb15132d050f8f98b16bdba4/configs/mainnet.yaml#L147) (approximately 18 days). By using `blobs` to post batches of compressed transactions, Optimistic rollups can significantly reduce the cost of writing transactions to L1.
201+
1. **State write**: Optimistic rollups publish transaction data and block headers (consisting of the previous block header hash, state root, batch root) to Ethereum as a `blob`, or "binary large object". [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844) introduced a cost-effective solution for including data on-chain. A `blob` is a new transaction field that allows rollups to post compressed state transition data to Ethereum L1. Unlike `calldata`, which remains permanently on-chain, blobs are short-lived and can be pruned from clients after [4096 epochs](https://github.com/ethereum/consensus-specs/blob/81f3ea8322aff6b9fb15132d050f8f98b16bdba4/configs/mainnet.yaml#L147) (approximately 18 days). By using blobs to post batches of compressed transactions, optimistic rollups can significantly reduce the cost of writing transactions to L1.
202202

203203
2. **Blob gas used**: Blob-carrying transactions employ a dynamic fee mechanism similar to the one introduced by [EIP-1559](https://eips.ethereum.org/EIPS/eip-1559). The gas fee for type-3 transactions takes into account the base fee for blobs, which is determined by the network based on blob-space demand and the blob-space usage of the transaction being sent.
204204

0 commit comments

Comments
 (0)