> ## 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 major protocol — Geth, Reth, Erigon, Bor, Nitro, AvalancheGo, Agave, 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 for the major protocols, not a frozen contract.

<Info>
  The client determines which **RPC namespaces** you can call. For example, Geth exposes `debug_*` while Erigon adds 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.
</Info>

This page lists the primary protocols. For a protocol not covered here, see its entry on the [Networks](/docs/protocols-networks) page or contact [support](https://chainstack.com/contact/) — the client can also be confirmed 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; exposes the `eth_*` and `debug_*` namespaces.
* Reth — the [Reth](https://github.com/paradigmxyz/reth) implementation, used for archive nodes.
* Erigon — the [Erigon](https://github.com/erigontech/erigon) implementation, available on [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** client — the [native Polygon client](https://github.com/0xPolygon/bor). It is interacted with using the [standard Ethereum JSON-RPC methods](https://ethereum.org/en/developers/docs/apis/json-rpc/).

<Warning>
  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).
</Warning>

## BNB Smart Chain

Archive nodes run **Reth** (the [`reth-bsc`](https://github.com/paradigmxyz/reth) implementation) — Chainstack migrated the BNB Smart Chain archive client from Erigon to Reth. It is interacted with using the [standard Ethereum JSON-RPC methods](https://ethereum.org/en/developers/docs/apis/json-rpc/).

## 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).

## 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.

## Gnosis Chain

* **Execution layer** — [Nethermind](https://github.com/NethermindEth/nethermind) (.NET implementation) for full nodes, and [Erigon](https://github.com/erigontech/erigon) for archive nodes. See the JSON-RPC reference in the [Nethermind](https://docs.nethermind.io/) and [Erigon](https://docs.erigon.tech/) documentation.
* **Consensus layer** — [Lighthouse](https://github.com/sigp/lighthouse).

## 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

The client is [Ronin](https://github.com/axieinfinity/ronin) — a Go Ethereum fork — interacted with using [Geth-style JSON-RPC methods](https://ethereum.org/en/developers/docs/apis/json-rpc/).

## Arbitrum

<Info>
  ### Stylus is supported

  Arbitrum nodes on Chainstack support Stylus.
</Info>

[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). 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/).

## 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

[Global Nodes](/docs/global-elastic-node) and [Trader Nodes](/docs/trader-node) run **op-reth** (built on [Reth](https://github.com/paradigmxyz/reth)). See the [Chainstack Optimism API reference](/reference/optimism-api-reference).

## zkSync Era

The client is [zkSync Era](https://github.com/matter-labs/zksync-era). Tracing is served through the `debug_*` namespace on archive nodes.

## 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/).

## 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 both the v2 and v3 APIs — see [Choosing TON API v2 or v3](/docs/ton-choosing-v2-or-v3).

## Sui

Sui runs the official [Sui full node](https://github.com/MystenLabs/sui). Chainstack serves Sui over both JSON-RPC and gRPC — see the [Sui gRPC endpoint](/docs/sui-grpc-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).

## Starknet

Chainstack's Starknet nodes implement the [Starknet JSON-RPC specification](https://github.com/starkware-libs/starknet-specs) **v0.8.1** (confirmed via `starknet_specVersion`).

## NEAR

NEAR runs the official [nearcore](https://github.com/near/nearcore) client, accessed via the [NEAR JSON-RPC API](https://docs.near.org/api/rpc/introduction).

## Tezos

Tezos runs [Octez](https://gitlab.com/tezos/tezos), the reference implementation, accessed through its RPC interface.

## Cardano

Cardano runs [cardano-node](https://github.com/IntersectMBO/cardano-node), the reference implementation.

## Stellar

Stellar runs [Stellar Core](https://github.com/stellar/stellar-core), accessed through the Horizon and RPC APIs.

## Filecoin

Filecoin runs [Lotus](https://github.com/filecoin-project/lotus), the reference implementation, which exposes a JSON-RPC API.

## 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). The same Bitcoin Core lineage serves the other UTXO chains on Chainstack (for example, Litecoin, Dogecoin, and Zcash via their respective Core clients).