Demonstration · Messaging

QryptoChatTM: sealed messaging

End-to-end messaging where every device holds its own lattice identity and the relay in the middle can only carry ciphertext. Type a message on one device and watch it seal, cross a relay that never sees the plaintext, and open on the other device.

per-device keyssealed record zero-knowledge relay

Demonstration: every message you type is encrypted with real AES-256-GCM in your browser and decrypted on the other pane. Nothing leaves this page. Device fingerprints (ML-DSA-87) and the session key exchange (ML-KEM-1024) are shown as labeled Sample values; those run inside the enclave.

Two devices, one sealed session

Send a message

Type into either device and send. The relay line below shows exactly what the server in the middle would see.

Device A
ML-DSA-87 fingerprint (sample): -
Device B
ML-DSA-87 fingerprint (sample): -

relay sees ciphertext only: (send a message)

Self-test pending.

How it holds up

What the design protects

  1. Per-device identity

    Each device has its own lattice key pair. A message is bound to the sending device with an ML-DSA-87 signature, so a compromised relay cannot forge a sender.

  2. Zero-knowledge relay

    The relay stores and forwards sealed records. It never holds a key that can open them, so it carries ciphertext and nothing more. The relay line above shows precisely that view.

  3. File transfer in the same session

    The same sealed-session discipline carries files as well as text, so a conversation and its attachments share one protected channel.

FLAG: not a live messaging service. This page seals and opens messages locally to demonstrate the workflow. A live deployment establishes per-device sessions with ML-KEM-1024, signs with ML-DSA-87, and routes through a zero-knowledge relay inside the enclave under XQ Zero Trust policy. Fingerprints shown here are sample values.

Put your team on it

We will stand up a sealed channel for your mission.