Chains & Networks
Instanodes runs production infrastructure across 50+ blockchains. EVM-compatible networks and non-EVM chains get the same operational standard, not an afterthought treatment for the second group. Every chain uses the same account, the same dashboard, and the same JSON-RPC/WebSocket pattern described in Get Started. You do not manage a separate relationship per chain. Both mainnet and testnet are available. The Instanodes team takes onboarding requests directly for chains not yet listed below.
Full chain list
| Chain | Type |
|---|---|
| Algorand | Non-EVM |
| Aptos | L1 |
| Arbitrum | L2 |
| Aurora | EVM-compatible |
| Avalanche | L1 |
| Base | L2 |
| Berachain | EVM-compatible |
| Bitcoin | Non-EVM |
| Bittensor | Non-EVM |
| Blast | L2 |
| BNB Smart Chain | EVM-compatible |
| Boba | L2 |
| Cardano | Non-EVM |
| Celo | EVM-compatible |
| Conflux | EVM-compatible |
| Cosmos | Non-EVM |
| Cronos | EVM-compatible |
| Dogecoin | Non-EVM |
| Ethereum | L1 |
| Fantom | EVM-compatible |
| Filecoin | Non-EVM |
| Flow | Non-EVM |
| Gnosis | EVM-compatible |
| Harmony | EVM-compatible |
| Hedera | Non-EVM |
| Injective | EVM-compatible |
| Internet Computer | Non-EVM |
| Kaspa | Non-EVM |
| Kava | EVM-compatible |
| Klaytn | EVM-compatible |
| Linea | L2 |
| Litecoin | Non-EVM |
| Manta | L2 |
| Mantle | L2 |
| Metis | L2 |
| Mode | L2 |
| Monad | EVM-compatible |
| Moonbeam | EVM-compatible |
| Near | L1 |
| Optimism | L2 |
| Osmosis | Non-EVM |
| Polkadot | Non-EVM |
| Polygon | L2 |
| Polygon zkEVM | L2 |
| PulseChain | EVM-compatible |
| Render | Non-EVM |
| Scroll | L2 |
| Sei | Non-EVM |
| Solana | Non-EVM |
| Stacks | Non-EVM |
| Starknet | L2 |
| Stellar | Non-EVM |
| Sui | L1 |
| Tezos | Non-EVM |
| Theta | Non-EVM |
| TON | Non-EVM |
| Tron | Non-EVM |
| VeChain | Non-EVM |
| XRP Ledger | Non-EVM |
| zkSync Era | L2 |
Chains marked with a link have a dedicated reference page with chain-specific notes and request examples. EVM chains follow the same eth_* JSON-RPC pattern shown throughout these docs. Non-EVM chains follow their own native RPC format. Confirm exact endpoint paths and available node types with the Instanodes dashboard when you deploy.
RPC shape differs by chain, the connection model doesn't
The transport pattern stays consistent across every chain: an HTTPS endpoint at https://{chain}.instanodes.io/v1/{api-key}, the same account, the same dashboard. What differs is the method set each chain's node software exposes:
-
Ethereum and other EVM chains, including Base, BNB Smart Chain, and Avalanche's C-Chain, speak standard JSON-RPC 2.0 with
eth_*methods:curl https://eth.instanodes.io/v1/{api-key} \ -X POST -H "Content-Type: application/json" \ --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}' -
Solana drops the
eth_prefix entirely. Methods likegetSlotandgetBalancereplace their EVM equivalents:curl https://solana.instanodes.io/v1/{api-key} \ -X POST -H "Content-Type: application/json" \ --data '{"jsonrpc":"2.0","method":"getSlot","params":[],"id":1}' -
Bitcoin uses no accounts and no
eth_methods, and runs as a UTXO-model chain queried through Bitcoin Core's own RPC interface:curl https://btc.instanodes.io/v1/{api-key} \ -X POST -H "Content-Type: application/json" \ --data '{"jsonrpc":"1.0","method":"getblockcount","params":[],"id":1}' -
Cosmos SDK chains expose a Tendermint RPC endpoint and a REST/LCD API instead of Ethereum-style JSON-RPC. A basic status check is a plain HTTPS GET, not a POST body:
curl https://cosmos.instanodes.io/v1/{api-key}/status -
Polkadot and other Substrate chains use their own method set, such as
chain_getHeaderandstate_getStorage. The names differ, but the JSON-RPC 2.0 request and response shape stays the same.
If your team needs a chain not on the list above, talk to us. Do not assume the chain is out of scope.