QERYX COMING SOON
OBSERVATORY

The server cannot read a word you send.

Post-quantum encrypted messenger, coming soon. Built on ML-KEM-1024

rerun open() on a corrupted frame

Real ChaCha20-Poly1305 (RFC 8439), compiled from Rust to WebAssembly, running in your browser. Same primitive family as the QERYX protocol; demo build, not the crypto-core module itself.

01 / THE FLOOR — WHAT THE RELAY HOLDS

  1. Seal

    Your device seals every message under ChaCha20-Poly1305 before it leaves your hand. The key is agreed with hybrid ML-KEM-1024 + X25519 and lives only on your devices. The relay receives ciphertext it cannot open — there is no server-side key to steal or subpoena.

    Tap the sealed thread above — the decrypt is real.

  2. Verify

    You will verify each peer once, in person, through the Entangled pairing, with no directory trusted: the two devices compare the check for you, and from then on it runs on its own.

    Read how the check runs.

  3. Carry

    Three hops will carry sealed bytes. Entry knows you but not your destination. Exit knows the destination but not you. The middle knows neither. Each hop peels one encryption layer — never the message.

    Watch the pulse cross the fleet.

02 / THE ECOSYSTEM — EIGHT CHAPTERS

Open any one. They are all sealed the same way.

Messenger · Q-RATCHET A fresh key for every message you send. QLEAP VPN · QLEAP Three hops. Zero memory. In development. QVault · QVAULT Secrets that stay on your iPhone, each sealed under its own key. Voice & Video · EVS-PQ binder Voice that stays clear when the network does not. Groups & Channels · Q-GROUPCIPHER Group names, descriptions, and every word sealed end-to-end. The carrier model · ZERO-KNOWLEDGE The server is a dumb encrypted blob relay. It cannot read messages. Q-Entangle-Bell · Q-ENTANGLE-BELL A CHSH-form co-possession ceremony above the hybrid handshake — in research. Trust Center · TRUST Conformance evidence an evaluator can verify line by line.

This is not QKD. Not quantum networking. Not quantum teleportation. We do not violate the no-communication theorem. Above an X25519 + ML-KEM-1024 floor that alone provides confidentiality, a session can fold a Tsirelson-bounded CHSH witness transcript into its key derivation — a deterministic classical co-possession witness, not physical entanglement; security never depends on it.

03 / KEY AGREEMENT — IN MOTION

Watch two clouds land on one secret.

Two independent systems converge on one shared secret. Scroll — the agreement runs as you pass.

Two independent systems converge on one shared secret — the X25519 + ML-KEM-1024 hybrid key agreement.

04 / THE DEADLINE — PUBLISHED, NOT PREDICTED

Read the deadline. It is already published.

The standards bodies have published the deadline. QERYX is built on the deadline algorithms.1

  1. 2022 CNSA 2.0 announced (CNSSP-15).
  2. 2024 FIPS 203 and FIPS 204 finalized (August 2024).
  3. 2027 ML-DSA-87 mandatory for new NSS signatures; ECDSA and RSA sunset.
  4. 2030 ML-KEM-1024 mandatory for NSS key establishment.
  5. NEXT QERYX: hybrid ML-KEM-1024 + X25519, ML-DSA-87 signing, forward secrecy per message. Coming soon.

Forward secrecy is the strongest layer of the harvest-now-decrypt-later defence: a key that no longer exists cannot be decrypted later.

CNSA 2.0 — asymmetric core conformant (ML-KEM-1024 + ML-DSA-87 at Category V; SHA-512 at or above the hash floor). The AEAD is ChaCha20-Poly1305 (RFC 8439), a documented deviation; the AES-256-GCM NSS suite is implemented and reserved as suite 0x0002. Pre-evaluation checklist (internal self-assessment against the NIAP Common Criteria bar, latest pass 2026-06): 0 algorithm-layer non-conformances, 5 documented deviations; no accredited-laboratory evaluation has begun.

  • KEM ML-KEM-1024
  • SIG ML-DSA-87
  • ECDH X25519
  • AEAD ChaCha20-Poly1305
  • HASH SHA-512
  • KDF HKDF-SHA-512

1 — sources: CNSSP-15, NIST FIPS 203/204. Verified line by line on /trust.

Step through.

Your keys will be born on your device. Coming soon.

Read the spec