From 5eac34c445f7a4ac6155b24354328e4a42668d95 Mon Sep 17 00:00:00 2001 From: soyboy Date: Thu, 23 Jan 2025 19:05:31 -0800 Subject: [PATCH] adding information about auto switching data availability type --- pages/builders/chain-operators/configuration/batcher.mdx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/pages/builders/chain-operators/configuration/batcher.mdx b/pages/builders/chain-operators/configuration/batcher.mdx index 9213c954c..b5cfdc653 100644 --- a/pages/builders/chain-operators/configuration/batcher.mdx +++ b/pages/builders/chain-operators/configuration/batcher.mdx @@ -27,7 +27,7 @@ The batcher policy defines high-level constraints and responsibilities regarding * **Data Availability Types**: * **Calldata** is generally simpler but can be more expensive on mainnet Ethereum, depending on gas prices. * **Blobs** are typically lower cost when your chain has enough transaction volume to fill large chunks of data. - * The `op-batcher` can toggle between these approaches by setting the `--data-availability-type=` flag or with the `OP_BATCHER_DATA_AVAILABILITY_TYPE` env variable. + * The `op-batcher` can toggle between these approaches by setting the `--data-availability-type=` flag or with the `OP_BATCHER_DATA_AVAILABILITY_TYPE` env variable. Setting this flag to `auto` will allow the batcher to automatically switch between `calldata` and `blobs` based on the current L1 gas price. * **Batch Submission Frequency** (`OP_BATCHER_MAX_CHANNEL_DURATION` and related flags): * Standard OP Chains frequently target a maximum channel duration between 1–6 hours. @@ -287,6 +287,10 @@ is `shadow`. ### data-availability-type + + Setting this flag to `auto` will allow the batcher to automatically switch between `calldata` and `blobs` based on the current L1 gas price. + + The data availability type to use for submitting batches to the L1. Valid options: `calldata`, `blobs`, and `auto`. The default value is `calldata`.