Loading...
private.me Docs
Get xBridge-PQ
PRIVATE.ME PLATFORM

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.

Government COMING SOON XorIDA Powered
Section 01

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

SENDER RSA / ECDH RECEIVER HARVEST NOW DECRYPT LATER QUANTUM COMPUTER Single-layer encryption = future plaintext
Section 02

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

PLAINTEXT L1: XorIDA SPLIT L2: ML-KEM ENCRYPT CHANNEL A (KEM+Share) CHANNEL B (KEM+Share) CHANNEL C (KEM+Share) DECRYPT + RECONSTRUCT
Section 03

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.

1. KEM SETUP ML-KEM-768 2. SPLIT XorIDA K-of-N 3. ENCRYPT KEM per Share 4. SEND N Channels 5. REBUILD Decrypt+Join LAYER 1: INFORMATION-THEORETIC XorIDA over GF(2) provides unconditional secrecy. Fewer than K shares reveal zero bits regardless of computational power. No quantum algorithm can break this because no computation is required. LAYER 2: POST-QUANTUM COMPUTATIONAL ML-KEM-768 (NIST FIPS 203) provides IND-CCA2 security against quantum computers. Each share encrypted with unique KEM-encapsulated shared secret. Breaking both layers simultaneously: impossible.
Key Security Properties
Defense-in-depth: Two independent security layers. XorIDA is information-theoretic (no computation breaks it). ML-KEM is post-quantum computational. Breaking one does not weaken the other.

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.
Section 04

Use Cases

🏛
Government
Classified Communications

Government classified channels protected against harvest-now-decrypt-later. Double-layer ensures that even decades-old captured traffic remains permanently unreadable.

Top Secret
💰
Finance
Financial Transaction Security

Protect high-value financial transactions and settlement data against quantum threats. SWIFT-level transaction security with 30+ year forward secrecy.

Forward Secrecy
🏥
Healthcare
Healthcare Data Long-Term Protection

Patient health records must remain confidential for decades. Double-layer ensures HIPAA compliance remains intact even against future quantum adversaries.

HIPAA Quantum-Safe
🏭
Infrastructure
Critical Infrastructure Upgrade

Power grids, water systems, and transportation networks upgrading to quantum-safe communications. xBridge-PQ provides a migration path that maintains backward compatibility.

Migration Path
Section 05

Integration

Quick Start
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);
}
establishQuantumChannel(config: { kemAlg: string, n: number, k: number }): Promise<QuantumChannel>
Establishes a double-layered quantum-safe channel. Layer 1: XorIDA K-of-N threshold split. Layer 2: ML-KEM encapsulation per share. Returns a QuantumChannel handle for subsequent key exchanges.
exchangeKey(channel: QuantumChannel, material: Uint8Array): Promise<Result<Uint8Array, ChannelError>>
Sends key material over the established double-layered channel. Each share is KEM-encrypted, distributed independently, and verified via HMAC-SHA256 before reconstruction. Returns the verified key material or a typed ChannelError.
Section 06

Security Properties

PropertyMechanismGuarantee
Layer 1 SecrecyXorIDA K-of-NInformation-theoretic (unconditional)
Layer 2 SecrecyML-KEM-768IND-CCA2 post-quantum
IntegrityHMAC-SHA256 per shareTamper detection before reconstruction
Forward SecrecyEphemeral KEM keysPer-session key isolation
Algorithm AgilityPluggable KEM layerDrop-in NIST standard upgrades
2
Independent security layers
768
ML-KEM security parameter
0 bits
Leaked from K-1 shares
FIPS 203
NIST standard compliance
VERIFIED BY XPROVE

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.

XPROVE AUDIT TRAIL
Every XorIDA split generates HMAC-SHA256 integrity tags. xProve chains these into a tamper-evident audit trail that proves data was handled correctly at every step. Upgrade to zero-knowledge proofs when regulators or counterparties need public verification.

Read the xProve white paper →
GET STARTED

Ready to deploy xBridge-PQ?

Talk to Ren, our AI sales engineer, or book a live demo with our team.

Book a Demo

© 2026 StandardClouds Inc. dba PRIVATE.ME. All rights reserved.

VERIFIABLE WITHOUT CODE EXPOSURE

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.

XPROVE CRYPTOGRAPHIC PROOF
Download proofs:

Verify proofs online →

Use Cases

🏛️
REGULATORY
FDA / SEC Submissions
Prove algorithm correctness for distributed systems without exposing trade secrets or IP.
Zero IP Exposure
🏦
FINANCIAL
Audit Without Access
External auditors verify secure operations without accessing source code or production systems.
FINRA / SOX Compliant
🛡️
DEFENSE
Classified Verification
Security clearance holders verify distributed systems correctness without clearance for source code.
CMMC / NIST Ready
🏢
ENTERPRISE
Procurement Due Diligence
Prove security + correctness during RFP evaluation without NDA or code escrow.
No NDA Required

Deployment Options

📦

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
Get Started →
🏢

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
Request Quote →

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.

Contact sales for assessment and pricing →