Supported chains

Each network has a service URL that you append to the gateway URL established during setup:

<gateway-url>/<service-url>

<gateway-url> includes your configured scheme, host, port, and any access prefix. The service URLs below have no leading slash; join the two parts with one slash. The same service paths apply to local, self-hosted, and managed gateways.

Service URLs

Search by name, chain ID or service URL, or filter to mainnets or testnets. Click a service URL to copy it.

Showing 41 of 41 networks across 20 chains

NetworkService URLChain ID

Ethereum mainnet 1

Hoodi testnet560048

Sepolia testnet11155111

Base mainnet 8453

Sepolia testnet84532

BNB Smart Chain mainnet 56

Testnet 97

Hyperliquid HyperEVM mainnet 999

Testnet 998

Arbitrum One 42161

Sepolia testnet421614

Robinhood Chain mainnet 4663

Testnet 46630

Monad mainnet 143

Testnet 10143

Polygon PoS mainnet 137

Amoy testnet80002

Arc mainnet 5042

Testnet 5042002

Avalanche C-Chain 43114

Fuji testnet43113

Plasma mainnet 9745

Testnet 9746

OP Mainnet 10

Sepolia testnet11155420

Ink mainnet 57073

Sepolia testnet763373

Flare mainnet 14

Coston2 testnet114

X Layer mainnet 196

Testnet 1952

Cronos mainnet 25

Testnet 338

Mantle mainnet 5000

Sepolia testnet5003

Tempo mainnet 4217

Moderato testnet42431

Morph mainnet 2818

Hoodi testnet2910

Gnosis mainnet 100

Chiado testnet10200

For Ethereum mainnet, the full address is <gateway-url>/service/ethereum. To change networks, replace the service path and update your library’s chain configuration to match. Mainnets and testnets are separate networks.

For subscriptions, append the service URL to your gateway’s WebSocket base address. See Subscriptions for usage and connection behavior.

A network not listed here

The table above is the documented network list. If a network is absent, this page does not establish support for it. Node operators looking to add capacity can follow Run a provider.