Blockchains can support multiple software implementations, or clients, that connect users to a blockchain network. Clients are developed to be compatible with specific protocols and serve different purposes, for example, allowing for faster transactions or managing smart contracts in an advanced manner. Some clients can also be optimized for different consensus algorithms. You can learn which clients are available for the most popular protocols on Chainstack below.
Ethereum node can have one of the following implementations of the execution layer client:
Polygon node can have one of the following client implementations:
BNB Smart Chain node can have one of the following client implementations:
The client is op-geth.
AvalancheGo is the node implementation for the Avalanche network in Golang. You can find API documentation in the Chainstack Avalanche API reference.
Arbitrum nodes on Chainstack support Stylus.
Nitro is the official node for the Arbitrum protocol. It is a fully integrated, complete layer 2 optimistic rollup system that includes fraud proofs, the sequencer, token bridges, advanced calldata compression, and more. For available methods, see Chainstack Arbitrum API reference and the official Arbitrum documentation.
The client is zkSync Era.
zkEVM Node is a Go implementation of a node that operates the Polygon zkEVM network. For available methods, see Chainstack zkEVM API reference and the official zkEVM documentation.
Global Nodes run op-erigon.
Trader Nodes run op-geth.
Solana — Solana’s official client is developed in Rust. JSON-RPC methods are available and can be found in the official Solana documentation. For JavaScript applications, use the @solana/web3.js library as a convenient interface for interacting with a Solana node using RPC methods.
The client is Geth-based.
Go Ronin — the Go Ethereum implementation that can be interacted with by using Geth JSON-RPC methods.
Aptos-core is the official client for the Aptos protocol. Developers can interact with Aptos via its various SDKs, including the TypeScript SDK, Python SDK, Rust SDK, and Unity SDK, or through its REST API.
Oasis-node is written in Go and serves as both a consensus and execution layer client. As it is EVM-compatible, it can be interacted with using the standard JSON-RPC API.
Lighthouse — the Rust implementation of the Beacon Chain client.
Nethermind — the Nethermind implementation. See the JSON-RPC methods reference in the official Nethermind documentation.
Cronos is a fully EVM-compatible chain. Developers can connect to it through the standard JSON-RPC API or via libraries like ethers.js, web3.js, and web3.py.
Sonic is the mainnet for Fantom and an EVM-compatible node client for Fantom’s network. It can be accessed via standard JSON-RPC methods.
Sonic is the mainnet for Fantom and an EVM-compatible node client for Fantom’s network. It can be accessed via standard JSON-RPC methods.
java-tron is the client. See also the TRON API reference.
Pathfinder is the node implementation for the Starknet protocol. It supports version v0.2.1
of the Starknet JSON-RPC specification with some minor differences.
The client is Geth-based.
Bitcoin Core connects to the Bitcoin peer-to-peer network to download and validate blocks and transactions. See available JSON-RPC API methods in the Bitcoin Postman collection.
Blockchains can support multiple software implementations, or clients, that connect users to a blockchain network. Clients are developed to be compatible with specific protocols and serve different purposes, for example, allowing for faster transactions or managing smart contracts in an advanced manner. Some clients can also be optimized for different consensus algorithms. You can learn which clients are available for the most popular protocols on Chainstack below.
Ethereum node can have one of the following implementations of the execution layer client:
Polygon node can have one of the following client implementations:
BNB Smart Chain node can have one of the following client implementations:
The client is op-geth.
AvalancheGo is the node implementation for the Avalanche network in Golang. You can find API documentation in the Chainstack Avalanche API reference.
Arbitrum nodes on Chainstack support Stylus.
Nitro is the official node for the Arbitrum protocol. It is a fully integrated, complete layer 2 optimistic rollup system that includes fraud proofs, the sequencer, token bridges, advanced calldata compression, and more. For available methods, see Chainstack Arbitrum API reference and the official Arbitrum documentation.
The client is zkSync Era.
zkEVM Node is a Go implementation of a node that operates the Polygon zkEVM network. For available methods, see Chainstack zkEVM API reference and the official zkEVM documentation.
Global Nodes run op-erigon.
Trader Nodes run op-geth.
Solana — Solana’s official client is developed in Rust. JSON-RPC methods are available and can be found in the official Solana documentation. For JavaScript applications, use the @solana/web3.js library as a convenient interface for interacting with a Solana node using RPC methods.
The client is Geth-based.
Go Ronin — the Go Ethereum implementation that can be interacted with by using Geth JSON-RPC methods.
Aptos-core is the official client for the Aptos protocol. Developers can interact with Aptos via its various SDKs, including the TypeScript SDK, Python SDK, Rust SDK, and Unity SDK, or through its REST API.
Oasis-node is written in Go and serves as both a consensus and execution layer client. As it is EVM-compatible, it can be interacted with using the standard JSON-RPC API.
Lighthouse — the Rust implementation of the Beacon Chain client.
Nethermind — the Nethermind implementation. See the JSON-RPC methods reference in the official Nethermind documentation.
Cronos is a fully EVM-compatible chain. Developers can connect to it through the standard JSON-RPC API or via libraries like ethers.js, web3.js, and web3.py.
Sonic is the mainnet for Fantom and an EVM-compatible node client for Fantom’s network. It can be accessed via standard JSON-RPC methods.
Sonic is the mainnet for Fantom and an EVM-compatible node client for Fantom’s network. It can be accessed via standard JSON-RPC methods.
java-tron is the client. See also the TRON API reference.
Pathfinder is the node implementation for the Starknet protocol. It supports version v0.2.1
of the Starknet JSON-RPC specification with some minor differences.
The client is Geth-based.
Bitcoin Core connects to the Bitcoin peer-to-peer network to download and validate blocks and transactions. See available JSON-RPC API methods in the Bitcoin Postman collection.