Loading...
private.me Docs
Get xAirGap
PRIVATE.ME PLATFORM

xAirGap: Air-Gapped Key Exchange

Exchange X25519 public keys between two parties using physical QR shares -- no electronic communication channel required. Double XorIDA tolerates courier failure. ECDH shared secret derived on reconstruction.

Physical-Digital COMING SOON XorIDA Powered X25519 ECDH
Section 01

The Problem

Key exchange protocols require electronic communication channels. In hostile environments, all electronic channels may be compromised, monitored, or unavailable. There is no standard protocol for bootstrapping cryptographic trust without electronics.

Diffie-Hellman, X25519, and every modern key agreement protocol assume a functioning electronic channel between parties. In embassies under surveillance, military field operations, or diplomatic contexts where SIGINT capabilities are assumed, this assumption fails catastrophically.

Manual key exchange via a single physical medium (USB drive, printed key) creates a single point of compromise. If the courier is intercepted, the entire key is exposed. There is no threshold protection, and there is no way to verify integrity without a pre-shared secret.

The Old Way

Public Key On USB drive or single paper Single Courier One path one failure point Intercepted Key exposed, MITM possible, trust broken
Section 02

The PRIVATE.ME Solution

Both parties generate X25519 keypairs locally, split their public keys via Double XorIDA into QR shares, and exchange shares through independent physical couriers. Each party reconstructs the other's public key from K shares and derives the ECDH shared secret.

xAirGap eliminates the single-courier vulnerability by distributing public key material across multiple independent paths. An adversary must intercept K-of-N couriers to learn the public key -- and even then, they only have the public key, not the private key needed to derive the shared secret.

The protocol is bidirectional: both parties simultaneously distribute their public key shares to each other. Once both sides reconstruct, X25519 ECDH produces an identical shared secret on both ends without any electronic communication.

The New Way

Party A X25519 keypair Double XorIDA Split pubkey A Courier 1 Courier 2 Courier 3 Party B Reconstruct A Party A Reconstruct B B's shares via couriers (same pattern) Party B X25519 keypair ECDH Shared secret
Section 03

How It Works

Symmetric bidirectional protocol: both parties independently generate, split, distribute, reconstruct, and derive. No coordination channel needed -- only pre-agreed courier logistics.

Step 1: Generate X25519 Keypair Both parties independently, offline Step 2: Split Public Key via Double XorIDA K-of-N QR shares per public key Step 3: Exchange via N Independent Couriers Physical, air-gapped, no electronics Step 4: Reconstruct Peer Public Key HMAC verify + Double XorIDA reassemble Step 5: Derive ECDH Shared Secret X25519(myPrivate, peerPublic)
Key Security Properties
No electronic channel: The entire key exchange occurs via physical couriers. No IP, no radio, no electronic emissions.
Courier tolerance: Up to N-K couriers can be intercepted or fail without compromising the exchange.
Forward secrecy: ECDH shared secret is derived fresh. Compromise of long-term keys does not reveal past session keys.
Section 04

Use Cases

🏛
Diplomacy
Embassy Key Exchange

Establish encrypted communication channels between embassies in monitored environments. QR shares distributed via diplomatic pouches across independent routes.

TEMPEST / SCIF
🪖
Defense
Military Field Operations

Forward-deployed units exchange keys without radio or satellite communication. QR shares delivered by separate runners. Operational security maintained in SIGINT-hostile environments.

COMSEC
🤝
Diplomacy
Diplomatic Comms Setup

New diplomatic channels bootstrapped via physical key exchange at summit meetings. Each delegation distributes QR shares through separate diplomatic staff.

Protocol-Grade
🏭
Critical Infrastructure
Facility Provisioning

High-security facilities (nuclear, biolab, data centers) provision cryptographic access via air-gapped key exchange. No network exposure during initial key setup.

Air-Gap Compliant
Section 05

Integration

Quick Start
import { initiateExchange, completeExchange } from '@private.me/xairgap';

// Party A: generate keypair and split public key
const exchange = await initiateExchange(myKeypair, {
  n: 3,        // total QR shares
  k: 2,        // threshold to reconstruct
});

// exchange.shares[0..2] -- give to couriers
// Each courier carries one QR share to Party B

// Party A: receive K shares from Party B's couriers
const result = await completeExchange(myKeypair, receivedShares);
// result.sharedSecret -- X25519 ECDH derived
initiateExchange(myKeypair: X25519Keypair, config: { n: number, k: number }): Promise<ExchangeShares>
Splits the local X25519 public key via Double XorIDA into N QR-printable shares. Each share includes HMAC integrity tag. Private key never leaves the local device.
completeExchange(myKeypair: X25519Keypair, peerShares: ExchangeShare[]): Promise<ExchangeResult>
Verifies HMAC on received shares, reconstructs the peer public key via Double XorIDA, and derives the X25519 ECDH shared secret. Returns the shared secret and peer public key.
Section 06

Security Properties

PropertyMechanismGuarantee
Key ConfidentialityDouble XorIDA split<K shares reveal zero bits of public key
Air-Gap CompliancePhysical-only transportNo electronic emissions during exchange
Courier ToleranceK-of-N thresholdN-K couriers can fail or be intercepted
ECDH SecurityX25519 Curve25519128-bit equivalent security for shared secret
IntegrityHMAC-SHA256 per shareTamper detection before reconstruction
0
Electronic emissions
128
Bit ECDH security
2.0x
Storage overhead
<1ms
Typical payload
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 xAirGap?

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

xAirgap 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/xairgap
  • 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 xAirgap 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 →