Skip to main content
Chainstack selects the node client for each protocol, and often per mode (full vs archive) and node type (Global Node, Trader Node, Dedicated Node). Clients evolve as protocols upgrade — so treat this page as the current picture, not a frozen contract.
The client determines which RPC namespaces you can call. For example, Geth exposes debug_* while Erigon and Reth add the Parity trace_* namespace, and Bor (Polygon) does not implement trace_* at all. See Debug and trace APIs for the per-protocol breakdown and Request units for how calls are billed.
This page lists every protocol you can deploy on Chainstack. For a protocol available only on request, see Dedicated Nodes on request or the Networks page. You can confirm the client at runtime with web3_clientVersion (EVM) or the chain’s equivalent.

​
Ethereum

Execution layer:
  • Geth — the Go Ethereum implementation, used for full nodes; exposes the eth_* and debug_* namespaces.
  • Reth — the Reth implementation, used for archive requests on Mainnet Global Nodes, and for all requests on Sepolia and Hoodi Global Nodes.
  • Erigon — the Erigon implementation, used for archive Dedicated Nodes; adds the Parity trace_* namespace on top of debug_*.
Consensus layer:
  • Lighthouse — the Rust implementation of the Ethereum Beacon Chain client.
See Debug and trace APIs for how the execution client affects available tracing methods.

​
Polygon

Polygon runs the Bor execution client — the native Polygon client — with Heimdall v2 for consensus. Bor is interacted with using the standard Ethereum JSON-RPC methods.
Chainstack has retired the Erigon client for Polygon — archive nodes now run Bor. Because Bor does not implement the Erigon-only Parity trace_* or erigon_* namespaces, use the debug_* methods (with flatCallTracer) instead. See Polygon methods and Debug and trace APIs.

​
BNB Smart Chain

BNB Smart Chain nodes run a different client for each mode:
  • BSC Geth — the BNB Chain fork of Go Ethereum, used for full nodes.
  • Reth — the reth-bsc implementation, used for archive nodes. Chainstack migrated BNB Smart Chain archive nodes from Erigon to Reth.
BNB Smart Chain Testnet Global Nodes run Reth for both modes. Both clients are interacted with using the standard Ethereum JSON-RPC methods.

​
opBNB

opBNB runs op-geth, BNB Chain’s fork of the OP Stack execution client.

​
Avalanche

AvalancheGo is the Go implementation of an Avalanche node. It exposes a Geth-compatible C-Chain API with a limited set of debug_trace* methods. See the Chainstack Avalanche API reference.

​
Arbitrum

​
Stylus is supported

Arbitrum nodes on Chainstack support Stylus.
Nitro is the official Arbitrum node — a fully integrated layer-2 optimistic rollup stack (fraud proofs, sequencer, token bridges, calldata compression). Blocks from before the Nitro upgrade are served by an Arbitrum Classic node, so Arbitrum uses arbtrace_* for pre-Nitro blocks and debug_* for post-Nitro blocks. See the Chainstack Arbitrum API reference and the official Arbitrum docs.

​
Robinhood Chain

Robinhood Chain runs Nitro, the Arbitrum client. Tracing is served through the debug_* namespace; the arbtrace_* and trace_* namespaces are not exposed. See Robinhood Chain methods.

​
Elysium

Elysium is an Arbitrum Orbit chain that settles to HyperEVM, and it runs Nitro, the Arbitrum client. Tracing is served through the debug_* namespace; the arbtrace_* and trace_* namespaces are not exposed. See Elysium methods and Elysium tooling.

​
Base

The execution client is base-reth-node (built on Reth) and the consensus client is base-consensus. Base introduced this native stack with the Azul upgrade (mainnet May 28, 2026), replacing op-geth and op-node.

​
Optimism, Unichain, and Zora

Global Nodes and Trader Nodes run op-reth — the OP Stack execution client built on Reth — with op-node for consensus. See the Chainstack Optimism API reference.

​
Celo

Celo runs op-reth in Celo’s build, with op-node for consensus.

​
Mantle

Mantle runs Mantle’s Geth-based op-geth execution client.

​
Linea

Linea runs Geth.

​
Scroll

The client is Geth-based (l2geth), accessed via the standard Ethereum JSON-RPC methods.

​
zkSync Era

The client is zkSync Era. Tracing is served through the debug_* namespace on archive nodes.

​
Starknet

Starknet runs Pathfinder. The default path and /rpc/v0_9 serve the Starknet JSON-RPC specification 0.9, and /rpc/v0_10 serves 0.10. Confirm the version on any path with starknet_specVersion.

​
Arc

Arc runs Circle’s arc-node: a Reth-based execution client with Malachite consensus. See Arc tooling.

​
Tempo

Tempo runs the tempo client, built on Reth.

​
Plasma

Plasma runs a Reth-based client. See Plasma methods.

​
Stable

Stable runs Stable’s Cosmos SDK-based node with an EVM module. See Stable methods.

​
MegaETH

MegaETH runs mega-reth, a Reth-based client. See MegaETH methods.

​
Monad

Monad runs the official Monad client. See Monad tooling.

​
Berachain

Berachain runs bera-reth for execution and BeaconKit for consensus.

​
Ink

Ink runs op-reth, the OP Stack execution client built on Reth, on Global Nodes. See Ink tooling.

​
World Chain

World Chain runs world-chain, a Reth-based OP Stack client.

​
Hyperliquid

HyperEVM JSON-RPC is served by nanoreth, a Reth-based client, on the /evm and /nanoreth paths. See Hyperliquid node configuration.

​
Kaia

Kaia runs the official Kaia client. web3_clientVersion reports it as Klaytn.

​
Gnosis Chain

  • Execution layer — Nethermind (.NET implementation), Erigon, and Reth, depending on the node type. Gnosis Chain Mainnet Global Nodes run Erigon, and Chiado Testnet Global Nodes run Nethermind. Trader Nodes run Nethermind in the full mode and Erigon in the archive mode. Dedicated Nodes on Gnosis Chain Mainnet run Nethermind or Reth in both modes. See the JSON-RPC reference in the Nethermind, Erigon, and Reth documentation.
  • Consensus layer — Lighthouse.

​
Cronos

Cronos is a fully EVM-compatible chain. Connect via the standard Ethereum JSON-RPC API or libraries like ethers.js, web3.js, and web3.py.

​
Harmony

The client is the Harmony Go implementation, interacted with using Geth-style JSON-RPC methods.

​
Fantom and Sonic

Both Fantom and Sonic run the Sonic client (Sonic is the successor network to Fantom Opera). It is EVM-compatible and accessed via the standard Ethereum JSON-RPC methods.

​
Ronin

Ronin runs conduit-op-reth, Conduit’s build of the OP Stack op-reth client, interacted with using the standard Ethereum JSON-RPC methods. On Ronin Saigon Testnet, early history is served by the legacy Ronin client, a Go Ethereum fork.

​
Solana

Solana runs Agave (the Anza validator client; reports as solana-core via getVersion). JSON-RPC methods are documented in the Solana docs. For clients, use @solana/kit or the classic @solana/web3.js — both are maintained.

​
TON

TON runs the official TON node. Chainstack exposes the v2 and v3 APIs, and on Global Nodes also TON API v4, served by ton-api-v4 over the node’s lite server — see Choosing TON API v2, v3, or v4.

​
Sui

Sui runs the official Sui full node. Chainstack serves Sui over JSON-RPC and gRPC — see the Sui gRPC endpoint. Sui Mainnet Global Nodes also serve GraphQL — see the Sui GraphQL endpoint.

​
Aptos

Aptos-core is the official Aptos client, accessed through its REST API and SDKs (TypeScript, Python, Rust).

​
TRON

java-tron is the client. See the TRON API reference.

​
Polkadot

Polkadot runs Parity’s Polkadot node, with Substrate API Sidecar for the REST interface.

​
XRP Ledger

XRP Ledger runs xrpld (formerly rippled), the reference XRP Ledger server. See XRP Ledger tooling.

​
Stellar

Stellar runs Stellar RPC (stellar-rpc) with a captive Stellar Core. Horizon is not served. See Stellar tooling.

​
Bitcoin

Bitcoin Core connects to the Bitcoin peer-to-peer network to download and validate blocks and transactions. See the available methods in the Bitcoin RPC methods reference.

​
Dedicated Nodes on request

Some protocols are available only as Dedicated Nodes deployed on request — contact us to set one up. Clients for the ones running on Chainstack today:
Last modified on October 6, 2026