Skip to Content
Networks and hosts
View Markdown source

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.

  • 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 native TRON HTTP API path families.
  • Network support means the Gateway can identify and route the network, not that every upstream implements every method or archive depth.

Host is the prefix shown in a dashboard Access Point. Always copy the complete deployed domain from the dashboard.

ChainNetworkChain IDJSON-RPC HostTRON HTTP API
EthereumMainnet1ether-jsonrpc
EthereumSepolia11155111ether-sepolia-jsonrpc
PolygonMainnet137poly-jsonrpc
PolygonAmoy80002poly-amoy-jsonrpc
BNB Smart ChainMainnet56bnb-jsonrpc
BNB Smart ChainTestnet97bnb-testnet-jsonrpc
ArbitrumMainnet42161arb-jsonrpc
ArbitrumSepolia421614arb-sepolia-jsonrpc
OptimismMainnet10op-jsonrpc
OptimismSepolia11155420op-sepolia-jsonrpc
BaseMainnet8453base-jsonrpc
BaseSepolia84532base-sepolia-jsonrpc
SolanaMainnet Betasol-jsonrpc
SolanaDevnetsol-devnet-jsonrpc
BitcoinMainnetbtc-jsonrpc
BitcoinTestnetbtc-testnet-jsonrpc
LitecoinMainnetltc-jsonrpc
LitecoinTestnetltc-testnet-jsonrpc
TRONMainnet728126428tron-jsonrpctron-httpapi
TRONNile3448148188tron-testnet-jsonrpctron-testnet-httpapi

Protocol capabilities

CapabilityCurrent status
Single JSON-RPC 2.0 call over HTTPSupported 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.

Last updated on