BNB Smart Chain

BNB Smart Chain is an EVM network in the Gateway catalog whose gas token is BNB. Both its Mainnet and Testnet are reachable over EVM JSON-RPC.

Networks and hosts

Copy the deployed Access Point from the dashboard. Each network has its own Gateway, and Route targets are filtered by chain, network, and protocol before selection.

Provider coverage

Four of the five Provider integrations reach BNB Smart Chain. Tenderly synchronizes Ethereum, Polygon, Arbitrum, Optimism, and Base only, so it produces nothing here.

A node outside those four vendors — self-hosted, an enterprise plan, or a vendor with no integration — can join the Route as a manual Endpoint.

Reads without an Endpoint

The EVM Endpoint-free set applies unchanged: eth_blockNumber, eth_getBlockByNumber with ["latest", false] or an explicit hexadecimal height and false, and debug_traceBlockByNumber with the callTracer configuration. Other parameter variants and cache misses continue to the Route. Endpoint-free RPC lists the exact forms and cache behavior.

Verify the network

curl '<bsc_access_point>' \
  -H 'Authorization: Bearer <app_api_key>' \
  -H 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'

Mainnet returns 0x38; Testnet returns 0x61. A mismatch usually means the Route holds an Endpoint pointing at the other network’s upstream.

Coverage boundary

The Gateway accepts one JSON-RPC 2.0 object per HTTP POST. Vendor extension methods, debug, trace, and archive history on BNB Smart Chain follow the upstream node and plan.

See Endpoints for inventory management and JSON-RPC for the request contract.