xdc.network valid

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/

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-20T22:15:06.625Z. Cached copy · Source on xdc.network

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

Machine-readable: GET /v1/resolve?q=xdc.network · GET /v1/domain/xdc.network · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for xdc.network:
1. POST https://agentwebmap.com/v1/sites/xdc.network/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://xdc.network/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/xdc.network/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/xdc.network).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.