Architecture geth v1.17.3 Developers Live Compare Downloads Quantum Company About Team Careers Blog Get in touch
XDC Innovation Labs / Downloads
Node software · Run XDC mainnet & Apothem testnet

Download XDC node software

Run the canonical XDPoSChain v2.7.0 production client via Docker, reproducible source builds, and chaindata snapshots — everything to run a full or validator node on XDC mainnet or Apothem testnet, sha256-verified.

Run with Docker Build from source Release notes →
Docker Source Snapshots Verify
Fastest path

One command, or pick your install

New operators can bootstrap a node in a single command. Everyone else: grab a binary, pull the Docker image, or build from source below.

System requirements click to expand
curl
Only prerequisite (1-command)
Linux / macOS
amd64 or arm64
Go 1.21+ · C compiler
Source builds only
~16 GB disk
Snapshot + headroom
curl -fsSL https://xdc.network/install.sh | bash
🐳

Docker (production)

The canonical XDPoSChain v2.7.0 client, pinned by content-addressable digest.

Docker commands
⌥

Build from source

Reproducible Go builds from the tagged XDPoSChain source — full control, any platform.

Source build
Docker · production client

XDPoSChain v2.7.0 canonical

The production consensus client, published to Docker Hub as xinfinorg/xdposchain. Pin by version tag for convenience, or by sha256: digest for reproducibility.

docker pull xinfinorg/xdposchain:v2.7.0
docker run -d --name xdc \ -p 8545:8545 -p 30303:30303 \ -v xdc-data:/work \ xinfinorg/xdposchain:v2.7.0

Exposes JSON-RPC on 8545 and P2P on 30303, persisting chaindata to the xdc-data volume. For a validator/masternode setup and environment flags, see the documentation.

Build from source

Compile XDPoSChain

Clone the tagged source and build with the Go toolchain. Produces the XDC binary in ./build/bin/.

git clone --branch v2.7.0 https://github.com/XinFinOrg/XDPoSChain.git cd XDPoSChain make XDC

Requires Go 1.21+ and a C compiler. The Go toolchain produces deterministic binaries from identical inputs — compare your sha256sum ./build/bin/XDC against the published image (see verification ↓).

Chaindata snapshots

Sync in hours, not days

Skip the full historical sync by importing a recent chaindata snapshot, then let your node catch up to the tip. Mainnet and Apothem testnet snapshots (full & archive) are published and refreshed regularly.

Mainnet
snapfull · PBSS
network ID 50 · zstd-compressed
Apothem
full & archive
testnet · network ID 51
~2 s
block time at tip
XDPoS 2.0 · deterministic finality
📦 Browse all snapshots → Run a node
Verification

Verify before you run

Every artifact is verifiable. Checksums catch download corruption; matching against the published source/Docker digest is your supply-chain guarantee.

✓

Cross-verify the production client

Confirm the XDC binary inside the Docker image matches its content-addressable digest:

docker pull xinfinorg/xdposchain@sha256:<digest> docker run --rm xinfinorg/xdposchain:v2.7.0 sha256sum /usr/local/bin/XDC

For a locally-built binary, diff your sha256sum ./build/bin/XDC against the image's reported hash. Identical inputs (Go version, source tag, build flags) yield identical output.

Next steps

After you download

Three natural next steps once you have the binary or image.

▶

Run with Docker

Step-by-step guide — Docker, bare-metal, and managed options. Platform matrix, FAQ and one-command installer.

Run guide →
⚈

geth RPC compare

Run live JSON-RPC parity checks between your new node and the reference endpoint to confirm correct sync.

RPC compare →