Error While Adding BNB Chain

[bhupender072]

I’m in the process of adding the BNB chain, but I’m encountering the following error:

{"time":"2025-08-14T04:32:26.393Z","severity":"info","message":"Start sanitizing of empty blocks. Batch size is 10","metadata":{"fetcher":"empty_blocks_to_refetch"}}

{"time":"2025-08-14T04:32:26.411Z","severity":"error","message":"Empty id in response: %{error: %{code: -32000, message: "batch length does not support more than 100"}, id: nil, jsonrpc: "2.0"}, stacktrace: {:current_stacktrace, [{Process, :info, 2, [file: ~c"lib/process.ex", line: 864]}, {EthereumJSONRPC, :sanitize_responses_reduce_fn, 2, [file: ~c"lib/ethereum_jsonrpc.ex", line: 578]}, {Enum, :"-reduce/3-lists^foldl/2-0-", 3, [file: ~c"lib/enum.ex", line: 2531]}, {EthereumJSONRPC, :sanitize_responses, 2, [file: ~c"lib/ethereum_jsonrpc.ex", line: 550]}, {EthereumJSONRPC.Receipts, :process_responses, 2, [file: ~c"lib/ethereum_jsonrpc/receipts.ex", line: 411]}, {EthereumJSONRPC.Receipts, :request_and_parse, 3, [file: ~c"lib/ethereum_jsonrpc/receipts.ex", line: 235]}, {Task.Supervised, :invoke_mfa, 2, [file: ~c"lib/task/supervised.ex", line: 101]}, {Task.Supervised, :reply, 4, [file: ~c"lib/task/supervised.ex", line: 36]}]}","metadata":{}}

ENV FILE

NETWORK=BNB Chain
SUBNETWORK=Mainnet
CHAIN_ID=56
DATABASE_URL=postgresql://blockscout:password@postgres:5432/bnb_db?ssl=false
ETHEREUM_JSONRPC_HTTP_URL=https://bsc-dataseed.binance.org
PORT=4000
DISABLE_NFT_MEDIA=true
ERLANG_COOKIE=blockscout_cookie

Batch size settings

ETHEREUM_BATCH_SIZE=20
ETHEREUM_JSONRPC_MAX_BATCH_SIZE=50
RECEIPT_BATCH_SIZE=50
LOGS_BATCH_SIZE=20

Could you please advise on how to resolve this, or let me know if any additional configuration is needed?

[ekawibisono]

Hello @bhupender072 , I apologize in advance, but the BNB explorer isn't working smoothly at the moment and is currently under development. You can check this website for support for the BlockScout explorer https://chains.blockscout.com/

[bhupender072]

Hi @ekawibisono,

Thank you for your reply.

I’m encountering another issue as well. For one of the chains, I’m getting a Too Many Requests error in Docker:

"time":"2025-08-19T04:27:51.778Z","severity":"error","message":"** (FunctionClauseError) no function clause matching in EthereumJSONRPC.HTTP.standardize_response/1\n (ethereum_jsonrpc 7.0.2) lib/ethereum_jsonrpc/http.ex:198: EthereumJSONRPC.HTTP.standardize_response(%{"code" => -32005, "data" => %{"see" => "https://infura.io/dashboard\"}, "message" => "Too Many Requests"})\n (elixir 1.17.3) lib/enum.ex:1703: Enum."-map/2-lists^map/1-1-"/2\n (ethereum_jsonrpc 7.0.2) lib/ethereum_jsonrpc/http.ex:55: EthereumJSONRPC.HTTP.chunked_json_rpc/3\n (ethereum_jsonrpc 7.0.2) lib/ethereum_jsonrpc/request_coordinator.ex:89: anonymous fn/4 in EthereumJSONRPC.RequestCoordinator.perform/4\n (ethereum_jsonrpc 7.0.2) lib/ethereum_jsonrpc/request_coordinator.ex:109: EthereumJSONRPC.RequestCoordinator.trace_request/2\n (ethereum_jsonrpc 7.0.2) lib/ethereum_jsonrpc.ex:618: EthereumJSONRPC.json_rpc/2\n (ethereum_jsonrpc 7.0.2) lib/ethereum_jsonrpc.ex:811: EthereumJSONRPC.fetch_blocks_by_params/3\n (stdlib 6.1) timer.erl:590: :timer.tc/2\n\n\nRetrying.","metadata":{"fetcher":"block_catchup","last_block_number":35089045,"first_block_number":35089054}}

Could you please advise how I can fix or work around this issue?

Thank you!

[ekawibisono]

hello @bhupender072 , Do you use chains BNB ? or Ethereum ?

[bhupender072]

Hi @ekawibisono ,
I’m currently working on adding the following chains to our Blockscout setup:

BNB Chain

Ethereum

Polygon

Mantle

Base

Arbitrum

Optimism

Avalanche

Linea

Fantom

Cronos

Metis

Please let me know if there are any specific configurations or best practices I should follow for multi-chain setup.

Thank you!

[ekawibisono]

hello @bhupender072 blockscout comming soon to support BNB Chain. for setup you can check this https://docs.blockscout.com/get-started/running-blockscout

Thanks

[bhupender072]

Hi @ekawibisono, I’m currently getting the “Too Many Requests” error across all chains. Is there any way to resolve or remove this limitation?

[ekawibisono]

hi @bhupender072 can you try active ENV backend this

INDEXER_DISABLE_PENDING_TRANSACTIONS_FETCHER=true

please Feedback after you add env this

[bhupender072]

Hi @ekawibisono, I have added this in my environment

backend-ethereum:
build:
context: D:/blockscout
dockerfile: ./docker/Dockerfile
args:
RELEASE_VERSION: 9.0.2
environment:
DATABASE_URL: postgresql://blockscout:password@db-ethereum:5432/ethereum_db?ssl=false
ETHEREUM_JSONRPC_HTTP_URL: https://mainnet.infura.io/v3/myapi
ETHEREUM_JSONRPC_WS_URL: wss://mainnet.infura.io/ws/v3/myapi
ETHEREUM_JSONRPC_FALLBACK_URLS: '["https://rpc.ankr.com/eth","https://cloudflare-eth.com","https://mainnet.infura.io/v3/myapi"]'
CHAIN_ID: '1'
BLOCKSCOUT_RPC_CONCURRENCY: 2
BLOCKSCOUT_RPC_RETRY_INTERVAL: 1000
DISABLE_PENDING_TRANSACTIONS_FETCHER: "true"
INDEXER_DISABLE_PENDING_TRANSACTIONS_FETCHER: "true"
depends_on:
- db-ethereum
command: >
sh -c "./bin/blockscout eval 'Explorer.ReleaseTasks.create_and_migrate()' && ./bin/blockscout start"

{"time":"2025-08-21T11:50:39.047Z","severity":"error","message":"GenServer Indexer.Block.Realtime.Fetcher terminating\n** (FunctionClauseError) no function clause matching in EthereumJSONRPC.HTTP.standardize_response/1\n (ethereum_jsonrpc 9.0.2) lib/ethereum_jsonrpc/http.ex:198: EthereumJSONRPC.HTTP.standardize_response(%{"code" => -32005, "data" => %{"see" => "https://infura.io/dashboard\"}, "message" => "Too Many Requests"})\n (elixir 1.17.3) lib/enum.ex:1703: Enum."-map/2-lists^map/1-1-"/2\n (ethereum_jsonrpc 9.0.2) lib/ethereum_jsonrpc/http.ex:55: EthereumJSONRPC.HTTP.chunked_json_rpc/3\n (ethereum_jsonrpc 9.0.2) lib/ethereum_jsonrpc/request_coordinator.ex:89: anonymous fn/4 in EthereumJSONRPC.RequestCoordinator.perform/4\n (ethereum_jsonrpc 9.0.2) lib/ethereum_jsonrpc/request_coordinator.ex:109: EthereumJSONRPC.RequestCoordinator.trace_request/2\n (ethereum_jsonrpc 9.0.2) lib/ethereum_jsonrpc.ex:722: EthereumJSONRPC.json_rpc/2\n (ethereum_jsonrpc 9.0.2) lib/ethereum_jsonrpc.ex:915: EthereumJSONRPC.fetch_blocks_by_params/3\n (indexer 9.0.2) lib/indexer/block/realtime/fetcher.ex:174: Indexer.Block.Realtime.Fetcher.handle_info/2\nLast message: :poll_latest_block_number\nState: %Indexer.Block.Realtime.Fetcher{block_fetcher: %Indexer.Block.Fetcher{broadcast: :realtime, callback_module: Indexer.Block.Realtime.Fetcher, json_rpc_named_arguments: [transport: EthereumJSONRPC.HTTP, transport_options: [http: EthereumJSONRPC.HTTP.Tesla,

[ekawibisono]

hi @bhupender072 Maybe this is a limitation of Infura, you can check what API limit is given to Infura

[bhupender072]

Hi @ekawibisono , I am using paid api.