opBNB RPC endpoint
opBNB (chain ID 204) is served over HTTPS POST JSON-RPC 2.0. Full nodes back the endpoint, supporting standard EVM methods. Free, paid plans, and PAYG include opBNB.
Network information
| Network | opBNB |
| Chain ID | 204 |
| Endpoint | https://rpc.solidrpc.io/YOUR_API_KEY/evm/204 |
| Access | Free and paid |
| Type | Mainnet · L2 |
| Native currency | BNB |
| Node types | Full |
| Methods | standard |
| Protocol | HTTPS JSON-RPC 2.0. WebSocket unavailable. WebSocket details |
Testing first? opBNB has a testnet on SolidRPC: opBNB Testnet.
Quickstart
Fetch the latest opBNB block number. Replace YOUR_API_KEY with a key from the dashboard. New accounts start on the Free plan, no card required (see getting started):
curl https://rpc.solidrpc.io/YOUR_API_KEY/evm/204 \
-X POST \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'Standard methods only
opBNB is served by full nodes only, there is no archive state, and trace_* and debug_* methods are not available on this chain. The standard EVM method set works as usual. See the networks page for per-chain coverage.
Limits and errors
Quotas and rate limits are account-wide, not per-chain. Method calls to opBNB draw from the same response-unit quota and rate limit as every other network. Error bodies are identical everywhere. See the error reference.