01 Publications
Read the protocol in the open.
Every security claim on this site resolves to a publication — versioned, dated, and cited to the source.
01The ledger — 12 papers, every one versioned
Take the index in order.
Each row carries its version, the date it was last revised, and the primitives it is responsible for. Open one and the paper states the same four values in its own header — the ledger and the document read from a single registry, so they cannot disagree.
12
PAPERS
13
PRIMITIVES
12
SOURCE ARTIFACTS
2026-10-02
LAST REVISION
Start here
- §04 Entanglement-Anchored Key Agreement Q-Entangle-Witness: folding Bell-certified public randomness — from a loophole-free Bell-test beacon or an operator-run CHSH device-behaviour witness — into session-key input material as an additive public co-factor strictly under a hybrid X25519 + ML-KEM-1024 secret. Auditable freshness that can never weaken the post-quantum floor, with the honest limits stated in full. X25519ML-KEM-1024ML-DSA-87HKDF-SHA-512
- §09 Q-Ratchet: Four Parallel Ratchets The per-message key ratchet behind every QERYX session: a symmetric HKDF chain every message in revision 1, with a classical X25519 ratchet, an ML-KEM-1024 epoch ratchet, and QRNG entropy re-injection that activate in protocol revision 2. Forward secrecy and post-compromise security arguments, header AAD binding, and skipped-key bounds. X25519ML-KEM-1024HKDF-SHA-512ChaCha20-Poly1305
- §11 The QERYX Protocol: Overview and Design Goals The tier-1 summary of the QERYX cryptographic protocol specification (Entangled v1): what the design carries, the one-paragraph threat model, seven design goals, and the map of per-chapter publications. Every load-bearing claim in the specification cites a path and line in the source. ML-KEM-1024ML-DSA-87X25519ChaCha20-Poly1305
- §12 The QERYX Threat Model The adversary QERYX is built against: full active network capability, a coercible server operator, and a cryptographically-relevant quantum computer. Twenty-one attack classes with their mitigations and residual risks, the defense-in-depth table, and — stated plainly — what QERYX cannot promise. ML-KEM-1024ML-DSA-87X25519
02The full index — filter it, or read it end to end
Read the whole record.
Every publication, newest revision first
- §01 Cryptographic Primitives and Parameter Sets The master table of every primitive QERYX instantiates — parameter sets, byte sizes, backend pinning, and the source citation for each. Covers the FIPS 204 §5.2 context-framing discipline, the labeled-HKDF catalog, the per-surface Argon2id ladder read from code, and what is deliberately absent from the build. ML-KEM-1024ML-DSA-87X25519ChaCha20-Poly1305
- §02 Known Limitations and Open Work The honesty layer of the specification: every gap between the spec and the code snapshot, enumerated — audit items not yet in code, items that require user action, cadence trade-offs, optional features off by default, open symptoms, and the next revision’s roadmap. Where spec and code diverge, code is canonical. ML-DSA-87Argon2idHKDF-SHA-512
- §03 FSOR: Cryptographic Erasure of Server-Held Ciphertext Forward-Secrecy Output Reset wraps the ciphertext of rows written through the REST send path in a per-conversation envelope whose key is derived at use and never stored. On destroy, the epoch advances: those rows’ bytes left in a backup, WAL or replica stay sealed to anyone without the operator’s master, which can still re-derive the key. Rows from other lanes and file-store blobs are deleted, never wrapped. With the honest limits stated. HKDF-SHA-512ChaCha20-Poly1305ML-DSA-87SHA-512
- §04 Entanglement-Anchored Key Agreement Q-Entangle-Witness: folding Bell-certified public randomness — from a loophole-free Bell-test beacon or an operator-run CHSH device-behaviour witness — into session-key input material as an additive public co-factor strictly under a hybrid X25519 + ML-KEM-1024 secret. Auditable freshness that can never weaken the post-quantum floor, with the honest limits stated in full. X25519ML-KEM-1024ML-DSA-87HKDF-SHA-512
- §05 CNSA 2.0 and FIPS Conformance Posture Every QERYX primitive mapped to its CNSA 2.0 line item and FIPS standard, with honest per-line markers — COMPLIANT, PARTIAL, DEVIATES — and the justification for each deviation. Includes the FIPS 140-3 module lifecycle, the self-test KAT set, and the two-build model. ML-KEM-1024ML-DSA-87AES-256-GCMSHA-512
- §06 Group Messaging: Sender Keys with Post-Quantum Rotation One sender key per member, ratcheted forward every message, re-encapsulated to the current member set via ML-KEM-1024 every 100 messages and on every membership change. Every sender-key handoff is signed under ML-DSA-87 over the conversation, sender, recipient, epoch and payload, and a receiver refuses an unsigned or mis-bound install; individual frames are authenticated by the sender-key chain itself, with per-frame authorship signatures implemented in crypto-core and staged for the client. Removed members cannot decrypt what comes next; new members cannot decrypt what came before. ML-KEM-1024ML-DSA-87ChaCha20-Poly1305HKDF-SHA-512
- §07 Identity and Key Transparency: Serpent ID, Profile ID, and the KTS Log The two-layer identity model — a device-only Serpent ID and a public Profile ID that is a truncated one-way SHA-256 of it — plus the Key Transparency System: an append-only SHA-384 Merkle log whose roots are signed under QERYX-KTS-ROOT-v1, verified against an operator key anchored in the client binary, with peer-to-peer root gossip that makes operator equivocation detectable. SHA-256ML-DSA-87SHA-384HMAC-SHA-256
- §08 Message AEAD, Frame Header v2, and the Padding Ladder The on-the-wire shape of one encrypted message: plaintext snapped to one of nine fixed buckets with crypto-random fill, ChaCha20-Poly1305 with the full Q-Ratchet header bound as AAD, and the Frame Header v2 outer envelope that makes peer re-registration detectable before decryption fails. ChaCha20-Poly1305HKDF-SHA-512
- §09 Q-Ratchet: Four Parallel Ratchets The per-message key ratchet behind every QERYX session: a symmetric HKDF chain every message in revision 1, with a classical X25519 ratchet, an ML-KEM-1024 epoch ratchet, and QRNG entropy re-injection that activate in protocol revision 2. Forward secrecy and post-compromise security arguments, header AAD binding, and skipped-key bounds. X25519ML-KEM-1024HKDF-SHA-512ChaCha20-Poly1305
- §10 The Hybrid Handshake: SP 800-227 Combiner and Entangled Session v1 Two interlocking handshake layers: a NIST SP 800-227 hybrid KEM combiner over X25519 + ML-KEM-1024, and Entangled Session v1 — the mutual-authentication handshake that mixes both peers’ OS-CSPRNG seed contributions, signs each leg under a distinct FIPS 204 context, and echoes nonces in constant time; it bootstraps the call plane, while the messenger bootstraps from the asynchronous signed-prekey handshake. X25519ML-KEM-1024ML-DSA-87HKDF-SHA-512
- §11 The QERYX Protocol: Overview and Design Goals The tier-1 summary of the QERYX cryptographic protocol specification (Entangled v1): what the design carries, the one-paragraph threat model, seven design goals, and the map of per-chapter publications. Every load-bearing claim in the specification cites a path and line in the source. ML-KEM-1024ML-DSA-87X25519ChaCha20-Poly1305
- §12 The QERYX Threat Model The adversary QERYX is built against: full active network capability, a coercible server operator, and a cryptographically-relevant quantum computer. Twenty-one attack classes with their mitigations and residual risks, the defense-in-depth table, and — stated plainly — what QERYX cannot promise. ML-KEM-1024ML-DSA-87X25519
No publication matches that filter.
Clear the filter to see the full index.
A paper on this ledger is a distillation of an in-repo specification chapter, not a substitute for it. Where the code has moved past the snapshot the paper was cut from, the paper says so in its own body rather than in a footnote here.