op-batcher: Add threshold for L1 blob base fee

[ak-akiyama]

Description

Add the new flag to op-batcher to cancel tx sending if the L1 blob base fee exceeds the threshold. The threshold value can be set using the cli argument --max-l1-blob-base-fee=n or the environment variable OP_BATCHER_MAX_L1_BLOB_BASE_FEE=n. If the threshold is set to 0 (default), no action will be taken.

This will be useful for the test L2 networks rolling up to the Sepolia network, which tends to have high blob fee rates.

Since no JSON-RPC method was found to get the L1 blob base fee, this implementation get the fee from the L2 GasPriceOracle contract:

optimism/packages/contracts-bedrock/src/L2/GasPriceOracle.sol

Lines 136 to 138 in 0db615d

	function blobBaseFee() public view returns (uint256) {
	return L1Block(Predeploys.L1_BLOCK_ATTRIBUTES).blobBaseFee();
	}

Tests

ak-akiyama@da79ba0#diff-6524d10e489e31223b0801a83152fb420341719ae1fb7deab8b74597b5c437e9R129-R156

[tynes]

Thanks for this PR! You should be able to calculate the current blob base fee using the following function here. Its not best to grab it from the L2, you can grab the latest L1 block header and pull the inputs from the header to pass into the linked function. This will allow you to delete a bunch of code spanning outside of the batcher in this PR. It would also be useful to have a max basefee config option as well, but no need to bloat this PR with multiple features. That could be done in a follow up.

[tynes]

I would like to eventually introduce the idea of "strategies" where you could implement more complex logic behind a common interface for when batches should be submitted. Definitely out of scope here but you could imagine expressing "submit the cheaper of calldata or blobs, under the max configured basefee/blobbasefee unless 20 mins pass, then submit no matter what" as a strategy

[ak-akiyama]

I'll close my PR since there is another excellent PR (#11219, #11059). Thank you for reviewing.