Deaddrop: Physical Dead Drop Messaging

The Problem

Digital communications leave metadata trails. Even end-to-end encrypted messaging reveals sender, recipient, timing, and frequency. No truly air-gapped messaging protocol exists for high-threat environments.

All encrypted messengers require electronic communication channels that produce metadata. Intelligence agencies, hostile governments, and sophisticated adversaries can exploit metadata — who talked to whom, when, and how often — without ever decrypting content.

Physical dead drops have existed for centuries, but they suffer from single-point-of-failure: if the drop location is compromised, the entire message is exposed. There is no threshold protection, no fault tolerance, and no cryptographic integrity verification.

The Old Way

The PRIVATE.ME Solution

Messages are AES-256-GCM encrypted, then split via Double XorIDA into QR shares placed at K separate physical locations. Single-use nonces via NonceStore prevent re-scanning. No electronics required for the drop itself. HMAC verification ensures integrity before reconstruction.

Deaddrop transforms the dead drop from a single-point vulnerability into a distributed threshold system. The sender places QR shares at independent locations. The recipient collects K shares from different sites. No single location contains enough information to reconstruct.

The NonceStore ensures each share is single-use: once scanned, the nonce is consumed and the share cannot be replayed. This prevents adversaries from covertly scanning and re-placing shares without detection. Each share carries an HMAC-SHA256 tag for tamper detection before reconstruction.

The New Way

How It Works

Five-step protocol: encrypt, split, place, collect, reconstruct. Every step is designed for air-gapped operation with no electronic communication between sender and recipient.

Use Cases

Integration

import { createDeadDropManager } from '@private.me/xdrop';

const manager = createDeadDropManager();

// Drop a message with a 2-of-3 split and a 24-hour TTL
const dropResult = await manager.dropMessage(message, 2, 3, {
  anonymousSender: true,  // unlink sender identity
  selfDestruct: true,    // destroy after first read
});

// Each share carries an HMAC-SHA256 tag; threshold K verified on pickup
if (dropResult.ok) {
  console.log('Pickup token:', dropResult.value.pickupToken);
}

// Recipient: pick up the message using the pickup token
const pickupResult = await manager.pickupMessage({
  identifier: dropResult.value.pickupToken,
  timestamp: new Date(),
});
// HMAC verified before reconstruction

// Check message status without reading (does not consume a read)
const statusResult = await manager.checkStatus(dropResult.value.pickupToken);

if (statusResult.ok) {
  console.log('Available:', statusResult.value.available);
  console.log('Reads remaining:', statusResult.value.remainingReads);
  console.log('Time until release:', statusResult.value.timeUntilRelease);
}

// Sender can delete a message before expiry
await manager.deleteMessage(dropResult.value.pickupToken, senderDid);

Implementation Status

Security Properties

Performance & Guarantees

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.

Ready to deploy Deaddrop?

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