From ff9a607698addc08507caf3d03231b0dd6fcfc7c Mon Sep 17 00:00:00 2001 From: romanito0410 <247900485+romanito0410@users.noreply.github.com> Date: Wed, 11 Mar 2026 22:34:46 -0600 Subject: [PATCH] fix: correct max-blocks-per-span-batch description and syntax examples --- chain-operators/guides/configuration/batcher.mdx | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/chain-operators/guides/configuration/batcher.mdx b/chain-operators/guides/configuration/batcher.mdx index e96d0f09b..615359d85 100644 --- a/chain-operators/guides/configuration/batcher.mdx +++ b/chain-operators/guides/configuration/batcher.mdx @@ -172,15 +172,12 @@ See the [span batch feature page](/op-stack/features/span-batches) to learn more #### max-blocks-per-span-batch -Indicates how many blocks back the batcher should look during startup for a -recent batch tx on L1. This can speed up waiting for node sync. It should be -set to the verifier confirmation depth of the sequencer (e.g. 4). The default -value is `0`. +Maximum number of blocks to add to a span batch. The default value is `0` (no maximum). - `--check-recent-txs-depth=` - `--check-recent-txs-depth=0` - `OP_BATCHER_CHECK_RECENT_TXS_DEPTH=0` + `--max-blocks-per-span-batch=` + `--max-blocks-per-span-batch=0` + `OP_BATCHER_MAX_BLOCKS_PER_SPAN_BATCH=0` #### compression-algo