SPECIFICATION & PROTOCOL

How ENCLAVE Works:
From Genesis to Obliteration

Discover the precise architectural journey that separates ENCLAVE from traditional permanent chat platforms. Seven distinct phases guarantee absolute confidentiality from inception to destruction.

Argon2id + HKDF-SHA256·96-bit Fresh IV Per Frame·Anti-Resurrection Tombstones
01

CREATE

The creator initiates an ephemeral room. The room salt and initial state are generated client-side using cryptographic entropy.

Tech spec: WebCrypto SubtleCrypto CSPRNG generates a 128-bit unique salt and 256-bit room secret.
02

SHARE

The room link and access pass are generated as two distinct factors and must be sent through separate communication channels.

Tech spec: Room identifier is in the URL. Access pass is kept strictly out-of-band and never sent to server.
03

JOIN

A participant opens the room link and enters the access pass provided out-of-band.

Tech spec: Client derives Key Wrapping Key via Argon2id (m=32MB, t=3, p=1) and HKDF-SHA256.
04

ESTABLISH

The client verifies the Auth Commitment with the relay and unwraps the Room Master Secret locally in memory.

Tech spec: Constant-time verification of auth hash. Zero cleartext pass transmitted to relay.
05

TALK

Messages are encrypted before leaving the device. The server routes opaque binary frames blindly.

Tech spec: AES-256-GCM authenticated payload with a fresh 96-bit random IV nonce per packet.
06

LEAVE

When a user departs, key material is zeroized in memory and departure packets notify remaining sockets.

Tech spec: CryptoKey references unpinned, memory buffers overwritten with random noise.
07

DESTROY

When the final participant disconnects or leaves, the room is permanently retired and cannot be revived.

Tech spec: Relay purges in-transit buffers and marks room identifier as non-recoverable tombstone.
03 / DUAL CHANNEL

A link isn't enough.

Conventional chat applications bundle access directly into a single URL. If that link is stored in browser history, scraped by preview crawlers, or intercepted on a clipboard, the conversation is exposed.

Every ENCLAVE room requires an independent access pass.

The pass is never included in the URL. This requires two independent pieces of information sent across two separate communication mediums.

Protocol Specification

The access pass is never included in query parameters (?pass=...), URL paths, or server access logs.

Channel Verification
Channel 1: Public Link
https://enclave.app/r/a9f2-c801
Public room identifier only
Channel 2: Access Pass
monolith-silence-zenith-cipher
Shared out-of-band via separate channel
MATHEMATICAL DERIVATIONAWAITING FACTORS
ROOM LINK + ACCESS PASS = ACCESS
Neither factor alone grants access to the room or ciphertexts.

Both independent factors are required to derive session keys on the client.

06 / EPHEMERAL LIFECYCLE

Every room has an ending.

When the final participant leaves, the room enters its definitive dissolution sequence. Key handles are wiped and the chamber ceases to exist.

01ACTIVE

ACTIVE

Participants present. End-to-end encrypted session active in RAM.

Memory keys stored in non-extractable CryptoKey handles.
02ENDING

ENDING

First participant leaves. Departure protocol armed.

Departure signal dispatched to remaining sockets.
03DESTROYING

DESTROYING

Final participant leaves. Zeroization protocol triggers.

Key references dropped, session memory overwritten.
04DESTROYED

DESTROYED

Room obliterated. Non-recoverable tombstone status.

Room ID retired permanently. Re-entry impossible.
Definitive Inaccessibility

When the final participant leaves, the room URL becomes inactive. No administrator or participant can revive, reconstruct, or view past ciphertexts.

Presence-First Architecture

ENCLAVE treats human conversation like spoken dialogue: temporary, contextual, and gone once the conversation concludes.

Experience it yourself

Create a room, share the pass, and observe the ephemeral destruction lifecycle in real time.