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 the native TRON HTTP API.
Host is the prefix shown in a dashboard Access Point. Always copy the complete deployed domain from the dashboard.
| Chain | Network | Chain ID | JSON-RPC Host | TRON HTTP API |
|---|---|---|---|---|
| Ethereum | Mainnet | 1 | ether-jsonrpc | — |
| Ethereum | Sepolia | 11155111 | ether-sepolia-jsonrpc | — |
| Polygon | Mainnet | 137 | poly-jsonrpc | — |
| Polygon | Amoy | 80002 | poly-amoy-jsonrpc | — |
| BNB Smart Chain | Mainnet | 56 | bnb-jsonrpc | — |
| BNB Smart Chain | Testnet | 97 | bnb-testnet-jsonrpc | — |
| Arbitrum | Mainnet | 42161 | arb-jsonrpc | — |
| Arbitrum | Sepolia | 421614 | arb-sepolia-jsonrpc | — |
| Optimism | Mainnet | 10 | op-jsonrpc | — |
| Optimism | Sepolia | 11155420 | op-sepolia-jsonrpc | — |
| Base | Mainnet | 8453 | base-jsonrpc | — |
| Base | Sepolia | 84532 | base-sepolia-jsonrpc | — |
| Solana | Mainnet Beta | — | sol-jsonrpc | — |
| Solana | Devnet | — | sol-devnet-jsonrpc | — |
| Bitcoin | Mainnet | — | btc-jsonrpc | — |
| Bitcoin | Testnet | — | btc-testnet-jsonrpc | — |
| Litecoin | Mainnet | — | ltc-jsonrpc | — |
| Litecoin | Testnet | — | ltc-testnet-jsonrpc | — |
| TRON | Mainnet | 728126428 | tron-jsonrpc | tron-httpapi |
| TRON | Nile | 3448148188 | tron-testnet-jsonrpc | tron-testnet-httpapi |
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 |
| JSON-RPC batch | Not supported |
| WebSocket | Not supported |
| Public gRPC | Not supported |
TRON /walletpbft/* | Not supported |
| Generic REST/HTTP API on non-TRON networks | Not supported |
Method support boundary
A supported network means the Gateway can identify it and route traffic to it. It does not mean every upstream implements every RPC method. The Gateway does not emulate node capabilities or enforce a fixed method allowlist.
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. Alchemy, QuickNode, Chainstack, and dRPC synchronize non-EVM networks according to their capabilities. Alchemy, QuickNode, and Chainstack produce both JSON-RPC and native HTTP API Endpoints for TRON; dRPC produces only the TRON JSON-RPC Endpoint. Networks outside this table are ignored.