Make XDC the most resilient and quantum-safe chain for real-world finance.
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. We work on both, on one network, ahead of the regulation and ahead of the threat.
Infrastructure resilience
Multi-client diversity on a modern go-ethereum foundation, so no single implementation or accreted technical-debt can halt the chain.
- 4 clients across 3 languages live on XDC mainnet — full client diversity (achieved).
- XDPoS re-based onto pristine go-ethereum v1.17.3, inheriting modern state, sync and wire-protocol work.
- Bit-exact consensus parity — identical state roots, receipts and block hashes against the canonical chain.
Post-quantum security
The XDC PQ Initiative and the XDSS-PQ standard — mapping and migrating XDC's quantum-exposed surface, prioritised by what cannot be re-signed later.
- An initiative and roadmap built on NIST-selected algorithms — not a claim that XDC is fully quantum-proof today.
- Long-lived trade documents first, because their 20–30 year validity makes harvest-now / decrypt-later a present risk.
- Targeted ahead of the EU PQC (2030), CNSA 2.0 and NIST deadlines.
Our ethos is simple: measured in production, not promised on a slide. The infrastructure figures on this site — disk, RPC, CPU and parity — are live readings from XDC mainnet nodes; the quantum work is framed honestly as an initiative and a roadmap.
Core infrastructure & the PQ initiative for the XDC ecosystem.
XDC Innovation Labs builds core node infrastructure and leads the post-quantum initiative for the XDC Network — the enterprise-grade, EVM-compatible Layer-1 originally launched by XinFin for global trade finance.
We are one contributor within a broader ecosystem, not the only entity building on XDC. The network is governed and supported by many independent teams, validators and community contributors. Our focus is deliberately narrow: multi-client resilience and quantum-safe cryptography.
Where we publish standards — such as XDSS-PQ — we develop them as open, NIST-aligned references so the wider ecosystem and institutional adopters can build on them.
What we work on
What we build on, and the standards we align to.
The references below are intentionally conservative — the network we build on, the open-source clients that give XDC its diversity, and the public cryptographic standards our PQ work aligns to. No co-authorship, endorsement or formal partnership is implied beyond what is stated.
Built on
XDC Network
The enterprise-grade, EVM-compatible Layer-1 (XDPoS consensus) we build core infrastructure and the PQ initiative for.
xdc.network →go-ethereum (GP5)
The XDPoS execution client re-based onto pristine go-ethereum v1.17.3 — our reference for bit-exact consensus parity.
GitHub →Erigon · Nethermind · Reth
The independent clients — Go, C#/.NET and Rust — that together give XDC mainnet full client diversity across implementations.
Standards we align to
NIST FIPS 203 / 204 / 205 / 206
The NIST post-quantum standards — ML-KEM, ML-DSA, SLH-DSA and FN-DSA (Falcon, draft) — that XDSS-PQ and our PQ roadmap are designed to align with.
MLETR
The UNCITRAL Model Law on Electronic Transferable Records — the legal frame for electronic trade documents that XDSS-PQ is designed to align with.
EU PQC · CNSA 2.0
Our PQ roadmap is positioned ahead of the EU PQC migration (2030) and CNSA 2.0 timelines that affect regulated finance — as context we target, not certifications we hold.
PQ migration roadmap →"Built on" denotes software and networks we use; "align to" denotes public standards we design toward. These are not endorsements, partnerships, or certifications.
Work with the team
hardening trade finance.
Meet the people behind the work, see the roles we're hiring for, or get in touch about the multi-client and post-quantum initiatives.