# XDC Innovation Labs

> XDC Innovation Labs makes the XDC Network measurably resilient and quantum-ready. Two headline pillars: infrastructure resilience (4 independent clients in 3 languages, all live/syncing XDC mainnet) and post-quantum security (the XDSS-PQ standard on NIST-selected algorithms). You can also run your own XDC node with a single command. Site (canonical): https://xdc.network/

Last updated: 2026-06-18

## Infrastructure resilience
- 4 independent clients in 3 languages, all live/syncing XDC mainnet: go-ethereum/GP5 and Erigon (Go), Nethermind (C#/.NET), Reth (Rust).
- Modern go-ethereum v1.17.3 re-baseline replaces the legacy 2018 Geth ~1.8.3 fork.
- Modern node ~303 GB on disk vs ~919 GB legacy full node (≈3× smaller).
- ~40× lower idle-head CPU than the legacy fork.
- Bit-exact consensus parity across clients — replayed mainnet blocks agree on the consensus-critical bytes.
- ~2-second block time with ~2-block deterministic BFT finality (XDPoS 2.0); ~2,000 TPS capacity.
- [Network architecture](https://xdc.network/network-architecture.html): Multi-client diversity — 4 clients / 3 languages on mainnet.
- [Modern geth migration](https://xdc.network/modern-geth-migration.html): The go-ethereum v1.17.3 re-baseline rationale, sourced and verified.
- [Geth compare](https://xdc.network/geth-compare.html): Live RPC, snapshot-size and bit-exact consensus-parity comparison, legacy vs modern vs Erigon.

## Post-quantum security
- XDSS-PQ — the XDC Digital Signature Standard (Post-Quantum) — is built on NIST-selected post-quantum algorithms.
- Ahead of the regulatory curve: DORA (in force), CNSA 2.0, the EU PQC roadmap (2030 target) and NIST deprecation (2035).
- [Post-quantum security](https://xdc.network/quantum.html): The XDSS-PQ standard and the XDC post-quantum migration.
- [Post-quantum FAQ](https://xdc.network/quantum-faq.html): Timelines, NIST algorithms, wallets, validators and XDSS-PQ — answered.

## Run a node

> Install and run an XDC Network blockchain node with a single command on Linux or macOS. The fastest way to run an XDC node is the one-command installer documented below. Source page (canonical): https://xdc.network/run

Chain snapshot freshness: rebuilt regularly; the ~16 GB snapshot fetched by the installer tracks within a short catch-up of the live chain tip (minutes behind head at restore time). Latest snapshots and their sha256 sums: https://xdc.network/snapshots/

## Quick start
curl -fsSL https://xdc.network/install.sh | bash

## What it does
- Auto-detects OS (Linux or macOS) and CPU (amd64/x86-64 or arm64/aarch64) and picks the matching geth build.
- Downloads a prebuilt geth node binary from xdc.network and verifies its sha256 before running it.
- Restores a recent ~16 GB chain snapshot instead of replaying every block.
- Starts syncing to the live XDC chain and reaches the tip in minutes, not days.
- No build, no scp, no compiling. The only prerequisite is curl.

## Facts
- Auto-detects Linux/macOS on amd64/arm64.
- sha256-verified geth binary, downloaded from xdc.network.
- Restores a recent ~16 GB chain snapshot (fast node).
- Measured full setup: 5m 32s (binary 1s, ~16 GB snapshot 2m 58s, extract 1m 44s), then a short catch-up to tip.
- Networks: XDC mainnet — chainId 50 (default); Apothem testnet — chainId 51.

## Platform support
- Linux: amd64 supported, arm64 supported.
- macOS: amd64 supported, arm64 supported.

## Manual / step-by-step path
curl -fsSL https://xdc.network/one.sh -o one.sh
bash one.sh setup    # fetch verified binary + restore snapshot
bash one.sh start    # start the node (auto-fetches geth if missing)
bash one.sh status   # sync %, current block, peers, stage timings
# other commands: stop, restart, logs, attach

## FAQ
- How do I run an XDC node? Run one command on Linux or macOS: curl -fsSL https://xdc.network/install.sh | bash. It auto-detects your OS and CPU, downloads a sha256-verified geth binary from xdc.network, restores a recent chain snapshot, and starts syncing to the live XDC chain. No build or scp is required.
- Which networks are supported? XDC mainnet (chainId 50) by default, and the Apothem testnet (chainId 51).
- What are the system requirements? Linux or macOS on amd64 (x86-64) or arm64 (aarch64). The only prerequisite is curl. Allow roughly 16 GB or more of free disk for the chain snapshot plus headroom for chain growth.
- Full node or fast node? A snapshot-restored fast node — it restores a recent ~16 GB chain snapshot instead of replaying every block, then catches up to tip.

## Links
- [Run a node (this page)](https://xdc.network/run): One-command XDC node installer.
- [Snapshots & binaries](https://xdc.network/snapshots/): sha256-verified downloads, rebuilt regularly.