Skip to main content
Docs

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

ChainType
AlgorandNon-EVM
AptosL1
ArbitrumL2
AuroraEVM-compatible
AvalancheL1
BaseL2
BerachainEVM-compatible
BitcoinNon-EVM
BittensorNon-EVM
BlastL2
BNB Smart ChainEVM-compatible
BobaL2
CardanoNon-EVM
CeloEVM-compatible
ConfluxEVM-compatible
CosmosNon-EVM
CronosEVM-compatible
DogecoinNon-EVM
EthereumL1
FantomEVM-compatible
FilecoinNon-EVM
FlowNon-EVM
GnosisEVM-compatible
HarmonyEVM-compatible
HederaNon-EVM
InjectiveEVM-compatible
Internet ComputerNon-EVM
KaspaNon-EVM
KavaEVM-compatible
KlaytnEVM-compatible
LineaL2
LitecoinNon-EVM
MantaL2
MantleL2
MetisL2
ModeL2
MonadEVM-compatible
MoonbeamEVM-compatible
NearL1
OptimismL2
OsmosisNon-EVM
PolkadotNon-EVM
PolygonL2
Polygon zkEVML2
PulseChainEVM-compatible
RenderNon-EVM
ScrollL2
SeiNon-EVM
SolanaNon-EVM
StacksNon-EVM
StarknetL2
StellarNon-EVM
SuiL1
TezosNon-EVM
ThetaNon-EVM
TONNon-EVM
TronNon-EVM
VeChainNon-EVM
XRP LedgerNon-EVM
zkSync EraL2

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 like getSlot and getBalance replace 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_getHeader and state_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.