xBridge-PQ: Post-Quantum Key Distribution
ML-KEM layered on top of XorIDA threshold sharing creates double-layered quantum-safe channels. Each share is XORed with a KEM-encapsulated shared secret for defense-in-depth.
The Problem
Current key exchange protocols (RSA, ECDH) will be broken by cryptographically relevant quantum computers. Harvest-now-decrypt-later is already an active nation-state strategy.
Intelligence agencies are capturing encrypted traffic today with the intent to decrypt it when quantum computers become available. A classified document encrypted with RSA-2048 or ECDH P-256 has a shelf life — once a sufficiently large quantum computer runs Shor's algorithm, every intercepted ciphertext becomes plaintext.
NIST has standardized post-quantum algorithms (ML-KEM, ML-DSA), but migrating from classical to post-quantum key exchange is a single-layer replacement. If ML-KEM itself is broken by future cryptanalysis, every channel relying solely on it is compromised. The industry needs defense-in-depth — not just a new algorithm, but a fundamentally different security model.
The Old Way
The PRIVATE.ME Solution
Double-layered quantum safety: XorIDA provides information-theoretic security (no computation breaks it), while ML-KEM adds a post-quantum computational layer. Breaking both simultaneously is impossible.
Layer 1: XorIDA splits data into K-of-N shares distributed across independent channels. This layer is information-theoretically secure — no quantum computer, no matter how powerful, can extract data from fewer than K shares. This is not a computational assumption; it is a mathematical proof.
Layer 2: Each share is additionally encrypted with an ML-KEM-encapsulated shared secret. Even if an adversary captures all N shares (breaking the channel separation), they still need to break ML-KEM to decrypt individual shares. The two layers are independent — breaking one does not help break the other.
The New Way
How It Works
A five-stage pipeline: ML-KEM key establishment, XorIDA threshold split, per-share KEM encryption, multi-channel distribution, and verified double-layer reconstruction.
Harvest-proof: Even if all traffic is captured today, the XorIDA layer ensures fewer than K shares reveal nothing — regardless of future quantum capabilities.
Algorithm agility: The KEM layer can be swapped (ML-KEM-512, ML-KEM-768, ML-KEM-1024) without changing the XorIDA architecture. Future NIST standards drop in seamlessly.
Use Cases
Government classified channels protected against harvest-now-decrypt-later. Double-layer ensures that even decades-old captured traffic remains permanently unreadable.
Top SecretProtect high-value financial transactions and settlement data against quantum threats. SWIFT-level transaction security with 30+ year forward secrecy.
Forward SecrecyPatient health records must remain confidential for decades. Double-layer ensures HIPAA compliance remains intact even against future quantum adversaries.
HIPAA Quantum-SafePower grids, water systems, and transportation networks upgrading to quantum-safe communications. xBridge-PQ provides a migration path that maintains backward compatibility.
Migration PathIntegration
import { establishQuantumChannel, exchangeKey } from '@private.me/xbridge-pq'; // Establish a quantum-safe channel (ML-KEM-768, 2-of-3) const channel = await establishQuantumChannel({ kemAlg: 'ML-KEM-768', n: 3, k: 2 }); // Exchange key material over the double-layered channel const result = await exchangeKey(channel, keyMaterial); if (result.ok) { // result.value contains verified key material deriveSessionKey(result.value); }
Security Properties
| Property | Mechanism | Guarantee |
|---|---|---|
| Layer 1 Secrecy | XorIDA K-of-N | Information-theoretic (unconditional) |
| Layer 2 Secrecy | ML-KEM-768 | IND-CCA2 post-quantum |
| Integrity | HMAC-SHA256 per share | Tamper detection before reconstruction |
| Forward Secrecy | Ephemeral KEM keys | Per-session key isolation |
| Algorithm Agility | Pluggable KEM layer | Drop-in NIST standard upgrades |
Verifiable Data Protection
Every operation in this ACI produces a verifiable audit trail via xProve. HMAC-chained integrity proofs let auditors confirm that data was split, stored, and reconstructed correctly — without accessing the data itself.
Read the xProve white paper →
Ready to deploy xBridge-PQ?
Talk to Ren, our AI sales engineer, or book a live demo with our team.
Ship Proofs, Not Source
xBridge-pq generates cryptographic proofs of correct execution without exposing proprietary algorithms. Verify integrity using zero-knowledge proofs — no source code required.
- Tier 1 HMAC (~0.7KB)
- Tier 2 Commit-Reveal (~0.5KB)
- Tier 3 IT-MAC (~0.3KB)
- Tier 4 KKW ZK (~0.4KB)
Use Cases
Deployment Options
SaaS Recommended
Fully managed infrastructure. Call our REST API, we handle scaling, updates, and operations.
- Zero infrastructure setup
- Automatic updates
- 99.9% uptime SLA
- Enterprise SLA available
SDK Integration
Embed directly in your application. Runs in your codebase with full programmatic control.
npm install @private.me/xbridge-pq- TypeScript/JavaScript SDK
- Full source access
- Enterprise support available
On-Premise Upon Request
Enterprise CLI for compliance, air-gap, or data residency requirements.
- Complete data sovereignty
- Air-gap capable deployment
- Custom SLA + dedicated support
- Professional services included
Enterprise On-Premise Deployment
While xBridge-PQ is primarily delivered as SaaS or SDK, we build dedicated on-premise infrastructure for customers with:
- Regulatory mandates — HIPAA, SOX, FedRAMP, CMMC requiring self-hosted processing
- Air-gapped environments — SCIF, classified networks, offline operations
- Data residency requirements — EU GDPR, China data laws, government mandates
- Custom integration needs — Embed in proprietary platforms, specialized workflows
Includes: Enterprise CLI, Docker/Kubernetes orchestration, RBAC, audit logging, and dedicated support.