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 | Complete method access |
|---|---|---|---|
| EVM | Ethereum, Polygon, BNB Smart Chain, Arbitrum, Optimism, Base | 3 Accelerator methods | Provider sync or manual setup |
| SVM | Solana | 3 Accelerator methods | Manual setup |
| UTXO | Bitcoin, Litecoin | 3 Accelerator methods | Manual setup |
| TRON | TRON | eth_blockNumber | Manual setup; an administrator must configure HTTP API routes |
Limits shared by every chain
- Only single JSON-RPC 2.0 calls over HTTP are supported; batch requests are not.
- WebSocket and public gRPC are not supported.
- The Gateway provides authentication, routing, health checks, load balancing, and failover. It does not emulate methods or historical data absent from an upstream.
- A new Gateway can read the small Accelerator method set. Cache misses, other methods, and writes require an Endpoint.
- 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