# BNB Smart Chain

> BNB Smart Chain Mainnet and Testnet through RPC Gateway, with chain IDs, the four supporting providers, and verification calls.

Canonical page: https://rpc.aurpay.net/docs/chains/bsc

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

| Network | Chain ID | JSON-RPC Host |
|---|---:|---|
| Mainnet | 56 | `bnb-jsonrpc` |
| Testnet | 97 | `bnb-testnet-jsonrpc` |

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.

| Provider | Mainnet | Testnet | Discovery model |
|---|:---:|:---:|---|
| [Alchemy](https://rpc.aurpay.net/docs/providers/alchemy.md) | Yes | Yes | Catalog-generated Endpoints |
| [QuickNode](https://rpc.aurpay.net/docs/providers/quicknode.md) | Yes | Yes | Account import, vendor status **active** only |
| [Chainstack](https://rpc.aurpay.net/docs/providers/chainstack.md) | Yes | Yes | Account import, vendor status **running** only |
| [dRPC](https://rpc.aurpay.net/docs/providers/drpc.md) | Yes | Yes | Catalog-generated load-balancer Endpoints |
| [Tenderly](https://rpc.aurpay.net/docs/providers/tenderly.md) | No | No | EVM subset without BNB Smart Chain |

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](https://rpc.aurpay.net/docs/endpoints.md#add-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](https://rpc.aurpay.net/docs/endpoint-free-rpc.md) lists the exact forms and cache behavior.

## Verify the network

```bash
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](https://rpc.aurpay.net/docs/endpoints.md) for inventory management and [JSON-RPC](https://rpc.aurpay.net/docs/json-rpc.md) for the request contract.