02 Guides
Run the verification yourself.
Each guide is an instrument you operate — verify a key, read a handshake, check a Bell transcript. No trust in QERYX required.
01The bench list — 5 procedures you can run
Pick a claim and check it.
A guide names the claim it tests, the exact steps that test it, and the result that would falsify it. Work through one and you hold a verdict you produced, not a statement we made.
02The procedures — each one ends in a verdict you produced
Take one and finish it.
Every guide, newest revision first
- 01 Understand the Handshake What actually happens in the second before your first message sends: two key exchanges run side by side — X25519 and ML-KEM-1024 — both peers contribute quantum-sourced entropy, and each leg is signed under its own FIPS 204 context. A plain-language walk through Entangled Session v1. X25519ML-KEM-1024ML-DSA-87HKDF-SHA-512
- 02 Verify a Bell Binding How a third party — an auditor, a journalist, a counterparty — checks that a session claiming a Bell binding really consumed a CHSH-verified transcript: fetch the transparency leaf, verify the Merkle inclusion proof, recompute S from the measurement counts, and confirm it sits in the accepted window. No trust in QERYX required. ML-DSA-87HKDF-SHA-512SHA3-256
- 03 Verify Your Safety Number The one manual step that closes the machine-in-the-middle door. What the safety number is, why the Key Transparency log cannot replace an out-of-band check, and the exact steps to run one — in person, over a call, or by QR. Five minutes, once per contact. ML-DSA-87SHA-512
- 04 What a Subpoena Yields The honest inventory of what a legal order against the QERYX relay can and cannot produce: ciphertext the order-holder cannot decrypt, blinded participant hashes, connection-level metadata — and, for destroyed conversations, envelope-locked bytes under a key that no longer exists. No dramatization; the table is the answer. ML-KEM-1024X25519ChaCha20-Poly1305HKDF-SHA-512
- 05 The Reviewer FAQ State-actor-tier reviewer questions, anticipated and answered: why Level 5 parameter sets, why hybrid rather than pure post-quantum, where formal verification stands, how side-channel classes are foreclosed, what happens when operator keys are compromised, and where to find a wire trace you can verify yourself. ML-KEM-1024ML-DSA-87HKDF-SHA-512
No guide matches that filter.
Clear the filter to see every guide.
Every procedure here runs against the shipping build on your own device or in your own browser. A guide that needed access we control would not be a verification, and it is not on this list.