THE PROTOCOL

Technical specifications of the Vanish ephemeral communication system.

End-to-End Encryption

Messages are encrypted with AES-256-GCM (Galois/Counter Mode) before storage. This provides both confidentiality and authentication. Encryption is hardware-accelerated with sub-millisecond overhead (~0.08ms per message), ensuring zero performance impact.

Ephemeral Architecture

Vanish operates on a "Memory-First" architecture. Unlike traditional chat apps that rely on persistent databases, Vanish utilizes high-speed, in-memory data structures that are designed to be volatile.

Real-time Sync

Communication is handled via a low-latency pub/sub protocol. Messages are broadcasted instantly to connected peers. Realtime messages are in-memory only and never persisted.

Redis-Backed TTL

Every room is assigned a strict Time-To-Live (TTL) at the infrastructure level. Once the timer expires, the Redis keys associated with the room are atomically deleted.

Zero-Persistence

Our protocol ensures that no backups, logs, or traces of the conversation exist once the room is destroyed. The deletion is final and irreversible.

Operational Flow

01

Session Initialization

A unique Room ID is generated using a cryptographically secure nanoid. A metadata hash is created in memory with a user-defined expiration timer.

02

Peer Connection

Users join the room using randomized identities. Connection tokens are managed in atomic sets to prevent unauthorized access and room overflow.

03

Atomic Destruction

Upon manual trigger or TTL expiration, the system executes a multi-key deletion command, wiping all messages, metadata, and connection tokens simultaneously.