# Chains

> Current RPC Gateway chains, networks, protocols, access hosts, setup paths, and limitations.

Canonical page: https://rpc.aurpay.net/docs/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](https://rpc.aurpay.net/docs/chains/tron.md#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](https://rpc.aurpay.net/docs/chains/ethereum.md), [Polygon](https://rpc.aurpay.net/docs/chains/polygon.md), [BNB Smart Chain](https://rpc.aurpay.net/docs/chains/bsc.md), [Arbitrum](https://rpc.aurpay.net/docs/chains/arbitrum.md), [Optimism](https://rpc.aurpay.net/docs/chains/optimism.md), [Base](https://rpc.aurpay.net/docs/chains/base.md) | 3 Endpoint-free RPC methods | App Provider association or manual Route selection |
| SVM | [Solana](https://rpc.aurpay.net/docs/chains/solana.md) | 3 Endpoint-free RPC methods | App Provider association or manual Route selection |
| UTXO | [Bitcoin](https://rpc.aurpay.net/docs/chains/bitcoin.md), [Litecoin](https://rpc.aurpay.net/docs/chains/litecoin.md) | 3 Endpoint-free RPC methods | App Provider association or manual Route selection |
| TRON | [TRON](https://rpc.aurpay.net/docs/chains/tron.md) | 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](https://rpc.aurpay.net/docs/chains/tron.md#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](https://rpc.aurpay.net/docs/endpoint-free-rpc.md); 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](https://rpc.aurpay.net/docs/authentication.md) and [JSON-RPC](https://rpc.aurpay.net/docs/json-rpc.md) for shared request details.