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.
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
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
How It Works
Symmetric bidirectional protocol: both parties independently generate, split, distribute, reconstruct, and derive. No coordination channel needed -- only pre-agreed courier logistics.
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.
Use Cases
Establish encrypted communication channels between embassies in monitored environments. QR shares distributed via diplomatic pouches across independent routes.
TEMPEST / SCIFForward-deployed units exchange keys without radio or satellite communication. QR shares delivered by separate runners. Operational security maintained in SIGINT-hostile environments.
COMSECNew diplomatic channels bootstrapped via physical key exchange at summit meetings. Each delegation distributes QR shares through separate diplomatic staff.
Protocol-GradeHigh-security facilities (nuclear, biolab, data centers) provision cryptographic access via air-gapped key exchange. No network exposure during initial key setup.
Air-Gap CompliantIntegration
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
Security Properties
| Property | Mechanism | Guarantee |
|---|---|---|
| Key Confidentiality | Double XorIDA split | <K shares reveal zero bits of public key |
| Air-Gap Compliance | Physical-only transport | No electronic emissions during exchange |
| Courier Tolerance | K-of-N threshold | N-K couriers can fail or be intercepted |
| ECDH Security | X25519 Curve25519 | 128-bit equivalent security for shared secret |
| Integrity | HMAC-SHA256 per share | Tamper detection before reconstruction |
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 xAirGap?
Talk to Ren, our AI sales engineer, or book a live demo with our team.
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.
- 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/xairgap- 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 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.