01
Initiative · audit and planning
Map the cryptographic surface
Identify dependencies across validators, wallets, bridges and applications. The published roadmap begins with an audit and risk assessment.
Read the source ↗RESEARCH / POST-QUANTUM
Think beyond
today’s cryptography.
A research initiative to prepare XDC’s signatures, applications and infrastructure for a post-quantum future.
i
Research and migration initiative. Public evidence includes a Falcon consensus proof of concept. It does not establish that XDC mainnet is quantum-safe today. Labs statement ↗
WHY IT MATTERS
Long-lived value
needs a long view.
Blockchain signatures protect transactions, operational keys and records. Future cryptographically relevant quantum computers could threaten commonly used public-key algorithms.
Preparing involves an inventory of cryptography, experiments with new algorithms, independent review, and coordinated adoption. Signature forgery and decryption are different risks and require different controls.
NIST post-quantum project ↗02
Planned · deployment unverified
Strengthen infrastructure
The roadmap proposes hybrid key exchange and stronger protection for operational keys. Targets are not evidence of completed deployment.
Read the source ↗03
Research · proposed upgrades
Evolve wallets and applications
Contributor research explores post-quantum transactions, wallet integration and EVM verification. Adoption requires coordinated engineering and review.
Read the source ↗04
Public proof of concept
Evaluate consensus signatures
The public poc_falcon branch experiments with Falcon block and quorum-certificate signatures. This is research evidence, not mainnet activation.
Read the source ↗THE CRYPTOGRAPHIC SURFACE
One algorithm change does not protect every layer.
Post-quantum preparation needs to follow the full path from user authorization to validator agreement and operational infrastructure.
Wallets and transaction signatures
A transaction-signature migration affects address handling, signing software, custody systems and recovery. Protecting consensus signatures alone does not automatically protect user accounts.
Contributor researchConsensus and client compatibility
The public Falcon experiment concerns consensus block and quorum-certificate signatures. A production change would also need interoperable behavior across the clients participating in consensus.
Inspect the public proof of conceptInfrastructure and confidential data
Transport security and key establishment have a different job from transaction signing. Inventory service connections, operational keys and long-lived confidential information separately.
NIST migration guidanceXDSS-PQ / DRAFT V1.0
A longer view for trade documents.
XDC Innovation Labs has published a proposed post-quantum signing design for long-lived trade records. The June 2026 specification remains a draft, subject to review and change.
Two signatures over one payload
The draft proposes ML-DSA and Falcon signatures over the same canonical document payload. Its verification rule requires both signatures to pass; it does not fall back to a single signature.
Read the XDSS-PQ draftDraft specification · Not a shipped product
Document protection has a defined scope
The proposal focuses on records such as bills of lading and letters of credit. It does not establish the truth of a document, ownership of physical goods, certification or a deployed XDC capability.
FROM EXPERIMENT TO UPGRADE
Make progress inspectable.
Use evidence-based milestones to assess readiness. This is an evaluation framework, not an announced XDC activation schedule.
Research evidence
Reproduce the experiment
Inspect the source branch and build assumptions. Repeat correctness and performance measurements with recorded hardware, parameters and test conditions.
Review required
Review the implementation
Evaluate key generation, signature validation, encoding, failure handling and implementation security. Algorithm standardization does not certify a particular integration.
Integration evidence
Validate the network transition
Test mixed-version behavior, client compatibility, wallet changes and recovery procedures in a controlled environment. A local benchmark does not establish network-wide readiness.
Deployment evidence
Publish activation evidence
Look for reviewed releases, an agreed upgrade process, operator instructions and observed adoption before describing protection as deployed.
YOUR ROLE IN PREPARATION
Useful work can start before activation.
Different participants own different parts of a cryptographic transition. Keep experiments separate from production keys and assets.
Researchers and client teams
Contribute reproducible tests, verification code and implementation review. Compare compatibility and resource costs across client implementations.
Explore client diversityWallet and application builders
Map signature dependencies and upgrade assumptions. Plan how users would authorize migration and recover access without assuming a future format is already supported.
XDC development resourcesOperators and enterprise teams
Maintain a cryptographic inventory and follow reviewed release guidance. Track identity, transport and custody dependencies alongside consensus software.
Follow the published roadmapGo to the source
Sources & further reading.
A standard is a starting point.
Deployment is another milestone.
ML-KEM
FIPS 203 · Key encapsulation
ML-DSA
FIPS 204 · Digital signatures
SLH-DSA
FIPS 205 · Digital signatures
Falcon
Used in XDC consensus experiments
NIST project status reviewed 22 October 2026. Algorithm alignment does not establish NIST certification of XDC. Source ↗
RESEARCH, EXPLAINED
Know what’s here.
Know what’s next.
Does post-quantum mean XDC runs on a quantum computer?+
No. Post-quantum cryptography uses algorithms intended to resist quantum attacks while running on conventional computers. The XDC initiative concerns cryptographic protection and migration, not quantum computation inside the blockchain.
What is the difference between a signature and key establishment?+
A digital signature helps verify authorization and message integrity. Key establishment lets parties derive a shared secret for secure communication. ML-KEM addresses key establishment; ML-DSA and SLH-DSA address signatures. These roles are not interchangeable.
Is there a confirmed activation date for a complete migration?+
The reviewed public sources do not establish a confirmed mainnet activation date. Published planning timelines differ, so this guide presents evidence and readiness milestones instead of treating target dates as completed upgrades.
Is XDC mainnet quantum-safe today?+
The reviewed public evidence does not establish that. XDC Innovation Labs describes an initiative and roadmap, while contributors have published a consensus proof of concept. Full migration needs implementation, security review and network adoption.
What does the Falcon proof of concept demonstrate?+
It explores Falcon signatures for consensus block signing and quorum certificates. It supports technical research, but does not establish production security, complete wallet protection or a deployed network upgrade.
Which post-quantum standards are finalized?+
NIST lists ML-KEM, ML-DSA and SLH-DSA as finalized standards. Its project page, updated August 2026, describes Falcon standardization as ongoing. Alignment with an algorithm is not NIST certification of XDC.
Why pursue multiple client implementations?+
Independent implementations can reduce shared software failure risks and give operators more choice. Actual network resilience also depends on tested compatibility, validator adoption and consensus thresholds—not the number of client names alone.
How should operators interpret client status?+
Treat the client list as Labs-reported development information. Check current releases, sync behaviour, consensus compatibility and validator support separately. The source includes inconsistent readiness labels, so verify suitability before changing production infrastructure.