You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like the env var INDEXER_OPTIMISM_L1_BATCH_BLOCKSCOUT_BLOBS_API_URL is required. If not set I see the following error in the logs and txn batches are not indexed:
{"time":"2024-04-30T01:56:10.166Z","severity":"error","message":"L2 genesis block number is undefined or invalid.","metadata":{"fetcher":"optimism_txn_batches"}}
However, using blobs for submitting batches is not required and a chain might opt to continue using calldata instead.
In some cases a blobs API might not even make sense, for e.g. if the chain is an L3 that rolls up to an L2 like OP mainnet.
Type of the installation
Docker
Type of the JSON RPC archive node
Geth
Type of the chain
L2
Link to the page
No response
Steps to reproduce
No response
Backend version
v6.4.0
Frontend version
v1.28.0
Elixir & Erlang/OTP versions
..
Operating system
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
Hi, Yes, INDEXER_OPTIMISM_L1_BATCH_BLOCKSCOUT_BLOBS_API_URL is required, but your error message tells that you haven't defined another env: INDEXER_OPTIMISM_L2_BATCH_GENESIS_BLOCK_NUMBER (defines the block number of BedRock upgrade, so if your OP chain starts from scratch with BedRock, the block number should be 0).
If your OP chain uses calldata instead of EIP-4844 blobs, you can workaround that by defining some dummy INDEXER_OPTIMISM_L1_BATCH_BLOCKSCOUT_BLOBS_API_URL (e.g. https://eth-sepolia.blockscout.com/api/v2/blobs). It won't be used if your batcher transactions don't have type 3 (EIP-4844 transactions).
Description
It looks like the env var
INDEXER_OPTIMISM_L1_BATCH_BLOCKSCOUT_BLOBS_API_URL
is required. If not set I see the following error in the logs and txn batches are not indexed:However, using blobs for submitting batches is not required and a chain might opt to continue using calldata instead.
In some cases a blobs API might not even make sense, for e.g. if the chain is an L3 that rolls up to an L2 like OP mainnet.
Type of the installation
Docker
Type of the JSON RPC archive node
Geth
Type of the chain
L2
Link to the page
No response
Steps to reproduce
No response
Backend version
v6.4.0
Frontend version
v1.28.0
Elixir & Erlang/OTP versions
..
Operating system
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: