> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Clients
> The node client Chainstack runs for each protocol — Geth, Reth, Erigon, Nethermind, Bor, Nitro, op-reth, AvalancheGo, Agave, Pathfinder, and more — and why the client determines which RPC methods are available.
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](/docs/debug-and-trace-apis) for the per-protocol breakdown and [Request units](/docs/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](#dedicated-nodes-on-request) or the [Networks](/docs/protocols-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](https://github.com/ethereum/go-ethereum) implementation, used for full nodes; exposes the `eth_*` and `debug_*` namespaces.
* Reth — the [Reth](https://github.com/paradigmxyz/reth) implementation, used for archive requests on Mainnet Global Nodes, and for all requests on Sepolia and Hoodi Global Nodes.
* Erigon — the [Erigon](https://github.com/erigontech/erigon) implementation, used for archive [Dedicated Nodes](/docs/dedicated-node); adds the Parity `trace_*` namespace on top of `debug_*`.
**Consensus layer:**
* Lighthouse — the [Rust](https://github.com/sigp/lighthouse) implementation of the Ethereum Beacon Chain client.
See [Debug and trace APIs](/docs/debug-and-trace-apis#ethereum) for how the execution client affects available tracing methods.
## Polygon
Polygon runs the **Bor** execution client — the [native Polygon client](https://github.com/0xPolygon/bor) — with [Heimdall v2](https://github.com/0xPolygon/heimdall-v2) for consensus. Bor is interacted with using the [standard Ethereum JSON-RPC methods](https://ethereum.org/en/developers/docs/apis/json-rpc/).
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](/docs/polygon-methods) and [Debug and trace APIs](/docs/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](https://github.com/bnb-chain/bsc), used for full nodes.
* Reth — the [`reth-bsc`](https://github.com/bnb-chain/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](https://ethereum.org/en/developers/docs/apis/json-rpc/).
## opBNB
opBNB runs [op-geth](https://github.com/bnb-chain/op-geth), BNB Chain's fork of the OP Stack execution client.
## Avalanche
[AvalancheGo](https://github.com/ava-labs/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](/reference/avalanche-getting-started).
## Arbitrum
### Stylus is supported
Arbitrum nodes on Chainstack support Stylus.
[Nitro](https://github.com/OffchainLabs/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](/reference/arbitrum-getting-started) and the [official Arbitrum docs](https://developer.arbitrum.io/).
## Robinhood Chain
Robinhood Chain runs [Nitro](https://github.com/OffchainLabs/nitro), the Arbitrum client. Tracing is served through the `debug_*` namespace; the `arbtrace_*` and `trace_*` namespaces are not exposed. See [Robinhood Chain methods](/docs/robinhood-methods).
## Elysium
Elysium is an Arbitrum Orbit chain that settles to HyperEVM, and it runs [Nitro](https://github.com/OffchainLabs/nitro), the Arbitrum client. Tracing is served through the `debug_*` namespace; the `arbtrace_*` and `trace_*` namespaces are not exposed. See [Elysium methods](/docs/elysium-methods) and [Elysium tooling](/docs/elysium-tooling).
## Base
The execution client is [`base-reth-node`](https://github.com/base/node) (built on [Reth](https://github.com/paradigmxyz/reth)) and the consensus client is [`base-consensus`](https://github.com/base/node). 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](/docs/global-elastic-node) and [Trader Nodes](/docs/trader-node) run **op-reth** — the OP Stack execution client built on [Reth](https://github.com/paradigmxyz/reth) — with op-node for consensus. See the [Chainstack Optimism API reference](/reference/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](https://github.com/ethereum/go-ethereum).
## Scroll
The client is [Geth-based](https://github.com/scroll-tech/go-ethereum) (`l2geth`), accessed via the [standard Ethereum JSON-RPC methods](https://ethereum.org/en/developers/docs/apis/json-rpc/).
## zkSync Era
The client is [zkSync Era](https://github.com/matter-labs/zksync-era). Tracing is served through the `debug_*` namespace on archive nodes.
## Starknet
Starknet runs [Pathfinder](https://github.com/software-mansion/pathfinder). The default path and `/rpc/v0_9` serve the [Starknet JSON-RPC specification](https://github.com/starkware-libs/starknet-specs) 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](https://github.com/circlefin/arc-node): a Reth-based execution client with Malachite consensus. See [Arc tooling](/docs/arc-tooling).
## Tempo
Tempo runs the [tempo](https://github.com/tempoxyz/tempo) client, built on [Reth](https://github.com/paradigmxyz/reth).
## Plasma
Plasma runs a Reth-based client. See [Plasma methods](/docs/plasma-methods).
## Stable
Stable runs Stable's Cosmos SDK-based node with an EVM module. See [Stable methods](/docs/stable-methods).
## MegaETH
MegaETH runs mega-reth, a Reth-based client. See [MegaETH methods](/docs/megaeth-methods).
## Monad
Monad runs the official [Monad](https://github.com/category-labs/monad) client. See [Monad tooling](/docs/monad-tooling).
## Berachain
Berachain runs [bera-reth](https://github.com/berachain/bera-reth) for execution and [BeaconKit](https://github.com/berachain/beacon-kit) for consensus.
## Ink
Ink runs op-reth, the OP Stack execution client built on [Reth](https://github.com/paradigmxyz/reth), on [Global Nodes](/docs/global-elastic-node). See [Ink tooling](/docs/ink-tooling).
## World Chain
World Chain runs [world-chain](https://github.com/worldcoin/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](/docs/hyperliquid-node-configuration).
## Kaia
Kaia runs the official [Kaia](https://github.com/kaiachain/kaia) client. `web3_clientVersion` reports it as `Klaytn`.
## Gnosis Chain
* **Execution layer** — [Nethermind](https://github.com/NethermindEth/nethermind) (.NET implementation), [Erigon](https://github.com/erigontech/erigon), and [Reth](https://github.com/paradigmxyz/reth), depending on the node type. Gnosis Chain Mainnet Global Nodes run Erigon, and Chiado Testnet Global Nodes run Nethermind. [Trader Nodes](/docs/trader-node) run Nethermind in the full mode and Erigon in the archive mode. [Dedicated Nodes](/docs/dedicated-node) on Gnosis Chain Mainnet run Nethermind or Reth in both modes. See the JSON-RPC reference in the [Nethermind](https://docs.nethermind.io/), [Erigon](https://docs.erigon.tech/), and [Reth](https://reth.rs/jsonrpc/intro) documentation.
* **Consensus layer** — [Lighthouse](https://github.com/sigp/lighthouse).
## Cronos
[Cronos](https://github.com/crypto-org-chain/cronos) is a fully EVM-compatible chain. Connect via the [standard Ethereum JSON-RPC API](https://ethereum.org/en/developers/docs/apis/json-rpc/) or libraries like ethers.js, web3.js, and web3.py.
## Harmony
The client is the [Harmony](https://github.com/harmony-one/harmony) Go implementation, interacted with using [Geth-style JSON-RPC methods](https://ethereum.org/en/developers/docs/apis/json-rpc/).
## Fantom and Sonic
Both Fantom and Sonic run the **[Sonic](https://github.com/0xsoniclabs/sonic)** client (Sonic is the successor network to Fantom Opera). It is EVM-compatible and accessed via the [standard Ethereum JSON-RPC methods](https://ethereum.org/en/developers/docs/apis/json-rpc/).
## 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](https://ethereum.org/en/developers/docs/apis/json-rpc/). On Ronin Saigon Testnet, early history is served by the legacy [Ronin](https://github.com/axieinfinity/ronin-archive) client, a Go Ethereum fork.
## Solana
Solana runs **[Agave](https://github.com/anza-xyz/agave)** (the Anza validator client; reports as `solana-core` via `getVersion`). JSON-RPC methods are documented in the [Solana docs](https://solana.com/docs/rpc). For clients, use [`@solana/kit`](https://github.com/anza-xyz/kit) or the classic [`@solana/web3.js`](https://github.com/solana-labs/solana-web3.js) — both are maintained.
## TON
TON runs the official [TON node](https://github.com/ton-blockchain/ton). Chainstack exposes the v2 and v3 APIs, and on Global Nodes also TON API v4, served by [ton-api-v4](https://github.com/ton-community/ton-api-v4) over the node's lite server — see [Choosing TON API v2, v3, or v4](/docs/ton-choosing-v2-or-v3).
## Sui
Sui runs the official [Sui full node](https://github.com/MystenLabs/sui). Chainstack serves Sui over JSON-RPC and gRPC — see the [Sui gRPC endpoint](/docs/sui-grpc-endpoint). Sui Mainnet Global Nodes also serve GraphQL — see the [Sui GraphQL endpoint](/docs/sui-graphql-endpoint).
## Aptos
[Aptos-core](https://github.com/aptos-labs/aptos-core) is the official Aptos client, accessed through its [REST API](https://aptos.dev/en/build/apis) and SDKs (TypeScript, Python, Rust).
## TRON
[java-tron](https://github.com/tronprotocol/java-tron) is the client. See the [TRON API reference](https://developers.tron.network/reference/background).
## Polkadot
Polkadot runs Parity's [Polkadot node](https://github.com/paritytech/polkadot-sdk), with [Substrate API Sidecar](/docs/polkadot-tooling#substrate-sidecar) for the REST interface.
## XRP Ledger
XRP Ledger runs [xrpld](https://github.com/XRPLF/rippled) (formerly rippled), the reference XRP Ledger server. See [XRP Ledger tooling](/docs/xrpl-tooling).
## Stellar
Stellar runs [Stellar RPC](https://github.com/stellar/stellar-rpc) (`stellar-rpc`) with a captive [Stellar Core](https://github.com/stellar/stellar-core). Horizon is not served. See [Stellar tooling](/docs/stellar-tooling).
## Bitcoin
[Bitcoin Core](https://bitcoincore.org/) 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](/reference/bitcoin-rpc-methods-postman-collection).
## Dedicated Nodes on request
Some protocols are available only as [Dedicated Nodes](/docs/dedicated-node) deployed on request — [contact us](https://chainstack.com/contact/) to set one up. Clients for the ones running on Chainstack today:
* Cardano — [cardano-node](https://github.com/IntersectMBO/cardano-node), with [Ogmios](https://github.com/CardanoSolutions/ogmios)
* Litecoin — [Litecoin Core](https://github.com/litecoin-project/litecoin)
* Zcash — [Zebra](https://github.com/ZcashFoundation/zebra), with [lightwalletd](https://github.com/zcash/lightwalletd)