Supported networks
The table below is the authoritative set of network combinations currently exposed by the Gateway. Every network supports JSON-RPC over HTTP POST. Only TRON Mainnet and Nile also support HTTP API. Endpoint-free RPC is currently enabled on mainnet networks only.
- RPC Gateway exposes the 20 chain-network combinations in the table below; every combination accepts one JSON-RPC call over HTTP
POST. - TRON Mainnet and Nile additionally expose the documented HTTP API path families.
- Endpoint-free RPC is enabled on mainnet networks; testnet support is not enabled.
- Network support means the Gateway can identify and route the network, not that every upstream implements every method or archive depth.
Account permissions determine which of these chains you can select and use. New accounts receive the administrator’s configured chain selection when they are created; later changes to that default do not change existing accounts. Administrator accounts retain access to all supported chains.
Host is the prefix shown in a dashboard Access Point. Always copy the complete deployed domain from the dashboard.
| Chain | Network | Chain ID | Hosts | Endpoint-free RPC |
|---|---|---|---|---|
| Ethereum | Mainnet | 1 | JSON-RPC: ether-jsonrpc | Enabled |
| Ethereum | Sepolia | 11155111 | JSON-RPC: ether-sepolia-jsonrpc | Not enabled |
| Polygon | Mainnet | 137 | JSON-RPC: poly-jsonrpc | Enabled |
| Polygon | Amoy | 80002 | JSON-RPC: poly-amoy-jsonrpc | Not enabled |
| BNB Smart Chain | Mainnet | 56 | JSON-RPC: bnb-jsonrpc | Enabled |
| BNB Smart Chain | Testnet | 97 | JSON-RPC: bnb-testnet-jsonrpc | Not enabled |
| Arbitrum | Mainnet | 42161 | JSON-RPC: arb-jsonrpc | Enabled |
| Arbitrum | Sepolia | 421614 | JSON-RPC: arb-sepolia-jsonrpc | Not enabled |
| Optimism | Mainnet | 10 | JSON-RPC: op-jsonrpc | Enabled |
| Optimism | Sepolia | 11155420 | JSON-RPC: op-sepolia-jsonrpc | Not enabled |
| Base | Mainnet | 8453 | JSON-RPC: base-jsonrpc | Enabled |
| Base | Sepolia | 84532 | JSON-RPC: base-sepolia-jsonrpc | Not enabled |
| Solana | Mainnet Beta | — | JSON-RPC: sol-jsonrpc | Enabled |
| Solana | Devnet | — | JSON-RPC: sol-devnet-jsonrpc | Not enabled |
| Bitcoin | Mainnet | — | JSON-RPC: btc-jsonrpc | Enabled |
| Bitcoin | Testnet | — | JSON-RPC: btc-testnet-jsonrpc | Not enabled |
| Litecoin | Mainnet | — | JSON-RPC: ltc-jsonrpc | Enabled |
| Litecoin | Testnet | — | JSON-RPC: ltc-testnet-jsonrpc | Not enabled |
| TRON | Mainnet | 728126428 | JSON-RPC: tron-jsonrpcHTTP API: tron-httpapi | Enabled |
| TRON | Nile | 3448148188 | JSON-RPC: tron-testnet-jsonrpcHTTP API: tron-testnet-httpapi | Not enabled |
Endpoint-free RPC is not currently enabled on testnets. Contact your administrator to request testnet support.
Protocol capabilities
| Capability | Current status |
|---|---|
| Single JSON-RPC 2.0 call over HTTP | Supported on every network above |
TRON /wallet/* | TRON Mainnet and Nile only |
TRON /walletsolidity/* | TRON Mainnet and Nile only |
TRON /v1/* | TRON Mainnet and Nile only; v1 is the TronGrid path family |
Method support boundary
A supported network means the Gateway can identify it and route traffic to it. Method coverage follows the configured upstream software, plan, archive depth, and enabled namespaces.
Actual method availability depends on:
- whether the route has a usable Endpoint;
- upstream software, plan, archive depth, and enabled namespaces;
- any method-specific JSON-RPC route configured for the call.
Provider sync imports only the intersection of networks supported by the vendor and this table; networks outside this table are ignored. Coverage differs by vendor: Alchemy and QuickNode cover all 20 combinations in this table, Chainstack covers 19 (Litecoin Testnet excluded), dRPC covers 16 over JSON-RPC, and Tenderly covers 10 EVM combinations only.