​

What’s Changed in op-batcher/v1.16.7

• all: upgrade op-geth, including shared tx-submission compatibility updates used by the batcher (#19844)
• chore(deps): bump op-geth again to v1.101702.1-rc.1 for this release candidate (#19992)
• chore(deps): bump google.golang.org/grpc to v1.79.3 (#19749)

• A feature where the batcher can choose a smarter, dynamic blob tip cap to use, based on recent market activity on L1. The feature can be enabled by setting OP_BATCHER_TXMGR_BLOB_TIP_CAP_DYNAMIC=true. By default, the existing static blob tip cap will be used. For more details, see https://github.com/ethereum-optimism/optimism/pull/18981 and https://github.com/ethereum-optimism/optimism/pull/18386.
• Several bugfixes and stability improvements.

[!TIP] If you use proxyd for the batcher’s L1 connection, we recommend upgrading to proxyd/v4.25.0 (this contains a non-critical bugfix and avoids noisy warning logs being emitted by the batcher).

• a new module for suggesting blob priority fee based on past blob transactions included in recent blocks. The new module is not active yet, currently it is only emitting logs comparing suggested fees with the configured fees for blob transactions.
• a fix for MaxChannelDuration tracking for large block backlogs.
• a fix for fully exiting the op-batcher process on critical throttling RPC errors.

[!NOTE] Please ensure the batcher is restarted at least once after op-node is upgraded, so it can load the latest rollup config at startup.

[!WARNING] This is an essential release to prepare for the L1 Fusaka fork on Sepolia.

[!IMPORTANT] The new flagOP_BATCHER_TXMGR_ENABLE_CELL_PROOFS must be set to “true” immediately after the Fusaka activation on L1.

[!IMPORTANT] All chain operators are strongly encouraged to upgrade their batchers to improve throttling behavior and mitigate worst-case spam attack scenarios.

​

Overview

• a transaction rebroadcasting feature which helps batcher transactions get included with less delay and lower cost.
• changes in the way the batcher interprets the sync status reported by the op-node
• other small bugfixes

[!WARNING] Operators should upgrade sequencers to at least op-node/v1.13.4 when updating to this version of the batcher. See #16413.

[!WARNING] The transaction rebroadcasting feature is enabled by default. To disable this feature, set TXMGR_REBROADCAST_INTERVAL to 0. See #16310.

[!WARNING] Rebroadcasting transactions can make memory spikes more likely. We recommend at least 4GB of memory for production deployments.

[!WARNING] This release replaces op-batcher/v1.13.0

[!WARNING] This release contained a CLI bug where the additional endpoints DA behavior would not activate. Please use op-batcher/v1.13.1

​

Isthmus

[!IMPORTANT] Chain operators need to upgrade their batchers before Isthmus activates on their chains. It is an optional upgrade until then.

[!NOTE] The Isthmus activation date for the Mainnet Superchain isn’t set yet. It won’t be before Ethereum Mainnet activates Pectra, so not before May 7, which is the current tentative Pectra activation date.

• changes the batcher’s throttling behaviour to purely event-driven instead of happening periodically.
• fixes a bug where the batcher cannot post to L1 networks which activated Pectra, triggered when the transaction is very small (typical in alt-DA settings).

• Minor changes into batcher metrics and logging, and
• Shortens the default duration to check the active sequencer. It has been lowered from 2min to 5 seconds, to avoid DA throttling being applied too late in case of a switch in sequencer.

​

🔴✨ Multi-Blob Batcher Pre-Release

      - OP_BATCHER_BATCH_TYPE=1 # span batches, optional
      - OP_BATCHER_DATA_AVAILABILITY_TYPE=blobs
      - OP_BATCHER_TARGET_NUM_FRAMES=6 # 6 blobs per tx
      - OP_BATCHER_TXMGR_MIN_BASEFEE=2.0 # 2 gwei, might need to tweak, depending on gas market
      - OP_BATCHER_TXMGR_MIN_TIP_CAP=2.0 # 2 gwei, might need to tweak, depending on gas market
      - OP_BATCHER_RESUBMISSION_TIMEOUT=240s # wait 4 min before bumping fees