Chains
RPC Gateway currently exposes 10 chains and 20 chain-network combinations. Every combination provides JSON-RPC over HTTP POST; TRON Mainnet and Nile also provide the native HTTP API.
Open a chain guide for its networks, Gateway hosts, verification call, Endpoint setup, and current limitations.
| Protocol | Chains | Endpoint-free methods | Upstream-backed access |
|---|---|---|---|
| EVM | Ethereum, Polygon, BNB Smart Chain, Arbitrum, Optimism, Base | 3 Endpoint-free RPC methods | App Provider association or manual Route selection |
| SVM | Solana | 3 Endpoint-free RPC methods | App Provider association or manual Route selection |
| UTXO | Bitcoin, Litecoin | 3 Endpoint-free RPC methods | App Provider association or manual Route selection |
| TRON | TRON | JSON-RPC eth_blockNumber; native HTTP API getnodeinfo and getblockbynum in their exact Endpoint-free RPC shapes | App Provider association or manual selection in the Gateway’s JSON-RPC and native HTTP API Routing views |
Shared protocol surface
- Every network accepts one JSON-RPC 2.0 call per HTTP
POST. - The Gateway provides authentication, routing, health checks, load balancing, and failover around the methods and historical data supplied by the upstream.
- Endpoint-free RPC serves its documented read set; configure an Endpoint for stable fallback coverage, additional methods, and writes.
- Associating a Provider with an App automatically maintains matching synchronized Endpoints in that App’s default JSON-RPC Routes and, for TRON, its native HTTP API Route. For manual control, select synchronized or manual Endpoints in each Gateway Route.
- Method availability ultimately depends on upstream software, plan, archive depth, and enabled namespaces.
See Authentication and JSON-RPC for shared request details.
Last updated on