Make XDC the most resilient and quantum-safe Layer-1 for regulated, real-world finance, ahead of the regulation and ahead of the threat.
Two clocks are ticking. Most chains hear neither.
XDC settles trade-finance instruments, documents and value that must stay verifiable for 20 to 30 years. That long horizon turns two slow-moving risks into existential ones.
Clock 1 - Infrastructure debt
Single-client networks are one bug away from a halt. Legacy node software carries years of accreted state-storage and sync debt: bloated disks, slow RPC, heavy hardware. Every year on old foundations raises the cost and the risk of running the network.
Compounding, every blockClock 2 - The quantum threat
A cryptographically-relevant quantum computer breaks the ECDSA signatures protecting keys, bridges and signed documents. Adversaries harvest encrypted data now to decrypt later, so 30-year trade documents signed today are already exposed.
Harvest-now, decrypt-laterA multi-client network, on a modern foundation.
XDC is the first XDPoS chain with full client diversity: four independent implementations across three languages, live on mainnet. In parallel, we re-based the XDPoS engine onto pristine go-ethereum v1.17.3 (branch reset/integration-1.17.3), inheriting a decade of upstream engineering, with bit-exact consensus parity.
4 clients, 3 languages
go-ethereum (GP5), Erigon, Nethermind and Reth, Go, C#/.NET and Rust, all live on XDC mainnet. No single implementation can halt the chain.
geth v1.17.3 re-baseline
XDPoS layered additively onto current go-ethereum: path-based state (PBSS), Pebble, freezer/ancients, snap sync and the modern wire protocol, without touching consensus.
Bit-exact parity
Block production, RLP encoding, hashes, rewards and masternode economics are unchanged. A parity harness verifies identical state roots, receipts and block hashes against canonical chain.
Measured, modern-geth node vs legacy full node
Live readings from XDC mainnet production nodes, synced to head.
Quantum-safe before the deadline, not after the break.
The XDC PQ Initiative introduces XDSS-PQ, a post-quantum signature and key standard built on NIST-selected algorithms. We are mapping and migrating XDC's full quantum-exposed surface, prioritised by what cannot be re-signed later: long-lived trade documents.
The exposed surface
Trade document signatures
ECDSA, secp256k1, 20-30yr lifespan
Validator masternode keys
ECDSA, secp256k1, 108 validator keys
Bridge & DAO governance
ECDSA multisig, cross-chain, indefinite
P2P node communications
ECDH, TLS 1.2-1.3, HNDL active now
The regulatory clock is already running
Financial entities must demonstrate robust cryptographic controls, the regulatory baseline for the trade-finance use XDC targets.
All new National Security Systems must be PQC-compliant on a fixed timeline.
Full PQC migration for EU critical infrastructure, the bar regulated trade-finance must meet.
ECDSA and all quantum-vulnerable algorithms deprecated from NIST standards.
Live on XDC mainnet.
Key numbers for the chain powering global trade finance. Gas price is pulled live from the XDC mainnet RPC every five seconds; the rest are fixed network facts.
We don't promise. We measure in production.
A clear line of sight across both pillars.
- 4 clients live on mainnet
- geth v1.17.3 re-baseline measured
- PQ Initiative v1.0 + XDSS-PQ draft
- Modern-geth fleet rollout
- Mainnet parity harness in CI
- PQ pilot - trade-doc signatures
- Multi-client validator support
- Hybrid quantum-safe validator & bridge keys
- Third-party security audits
- Within 1 minor of upstream geth
- XDSS-PQ v1 in production
- Regulated-finance GA - ahead of EU PQC
H1-2026 milestones are shipped or measured; later milestones are the active plan.
The window and the work rarely line up. Right now they do.
The window is open
Regulation (DORA, CNSA 2.0, EU PQC) and infrastructure debt are converging on the same deadline. Whoever solves both first owns regulated, real-world finance on-chain.
The niche makes it existential
XDC's 20-30 year trade documents turn "someday" risks into today's problem, and turn solving them into a durable, defensible moat that generic L1s can't claim.
The proof is already in production
Four clients live. A modern node measured 3× smaller and ~40× lighter on CPU, bit-exact. This is an execution team that ships and measures, not one that promises.
Build, run, and explore XDC.
Four ways to participate in the most resilient, quantum-safe trade-finance chain, from running infrastructure to shipping contracts to reading the source.
Run a node
Full node or masternode: snapshots, the one-command installer, and systemd templates.
Run a node →Build on XDC
EVM-compatible. Ship your Solidity contracts and tooling with ~2-second finality.
Read the docs →Explore the code
Four open-source clients in three languages. Audit, contribute, or run your own.
View on GitHub →Post-quantum research
XDSS-PQ, the quantum-safe signature standard hardening XDC for the next thirty years.
Learn about XDSS-PQ →Questions, answered.
How fast is XDC Network's block time?
XDC Network runs the XDPoS 2.0 consensus engine with a ~2-second block time and fast, deterministic BFT finality (about two blocks). Its current throughput capacity is approximately 2,000 TPS.
How many node clients run on XDC mainnet?
Four independent execution clients across three languages — go-ethereum (GP5) and Erigon in Go, Nethermind in C#/.NET, and Reth in Rust — all sync XDC mainnet. XDC is the first XDPoS chain with full client diversity, so no single implementation can halt the network.
What is XDSS-PQ?
XDSS-PQ is XDC's post-quantum signature and key standard, built on NIST-selected algorithms. It is being introduced ahead of regulatory deadlines including DORA, CNSA 2.0 and the EU PQC roadmap, prioritizing long-lived trade-finance documents that must stay verifiable for 20–30 years.
How much lighter is the modern XDC node?
On XDC mainnet production nodes, the modern go-ethereum v1.17.3 re-baseline measures about 303 GB on disk versus roughly 919 GB for a legacy full node (about 3× smaller), with around 40× lower CPU at idle head — measured in production with bit-exact consensus parity.
Is XDC Network quantum-safe today?
XDC is actively migrating to post-quantum security through the XDSS-PQ standard rather than claiming it is finished. The quantum-exposed surface — trade-document signatures, validator and bridge keys, and node communications — is being mapped and migrated, prioritized by what cannot be re-signed later.
Building the resilient, quantum-safe future of trade finance.
XDC Innovation Labs is hardening XDC on two fronts: multi-client infrastructure and post-quantum security. Explore the engineering, or get in touch.