04 Security · Q-Entangle-Bell
Bind the key to a measurement nobody can precompute.
QERYX is the first shipping commercial messenger to bind session keys to a CHSH-verified, Tsirelson-window-validated Bell-game transcript both peers seed and any auditor can verify.
01The claim — layered above the hybrid floor
Bound above the floor. Never instead of it.
Every session key is bound to a CHSH-verified, Tsirelson-window-validated Bell-game transcript both peers seed and any auditor can verify — and to an operator-signed transcript from real quantum processors where the v2 lane is active. The binding sits ABOVE the X25519 + ML-KEM-1024 hybrid floor; the classical floor never weakens. Breaking a session requires breaking both X25519 and ML-KEM-1024.
CNSA 2.0 disallows QKD for National Security Systems — a position we agree with. Q-Entangle-Bell is not QKD: it adds a verifiable transcript to the key derivation, and its removal would leave the hybrid handshake exactly as strong.
02Run it — SHAKE256 rounds, SHA3-256 chain
Run the Bell game yourself.
Real math, in this browser: every round re-derives from the two peer seeds via SHAKE256, rounds chain by SHA3-256, and VERIFY CHAIN recomputes the whole transcript. Push the S value past the classical bound of 2 and watch the verdict change.
Run the Bell test yourself.
Two peers seed a CHSH ritual; every round re-derives from those seeds and chains by SHA3-256. Verify the chain, then fetch a signed pulse from the live beacon and verify that too.
PEER A — · PEER B — · FUSED SHA3-256 —
S = —
awaiting rounds
- E(a,b)
- —
- E(a,b′)
- —
- E(a′,b)
- —
- E(a′,b′)
- —
- PAIRS
- 0
a 0° · a′ 45° · b 22.5° · b′ 67.5° — CHSH-optimal settings, one round = 512 pairs, settings switched per pair.
Honesty note: your browser cannot hold entangled photons — this bench samples the exact quantum statistics (E = cos 2(a−b)) versus a genuine local hidden-variable model (λ uniform, deterministic outcomes). The point it proves is mathematical and real: no local model crosses 2; quantum statistics do. Every signed pulse below carries a backend label — today’s beacon pulses say local-sim, and the verifier shows it. When hardware pulses ship, that label is how you will know.
Recompute a signed beacon pulse in this browser
Your browser fetches one pulse, recomputes its SHA3-256 self-commitment from the raw bytes, checks the hash-chain link, and re-derives the CHSH Bell-violation flag exactly as the signer did.
This button is the only network request this instrument ever makes — one GET to https://quantumentanglement.io/pulse/latest, a QERYX-owned origin, and only when you press it.
Press FETCH & VERIFY to pull the latest signed pulse from the beacon and recompute it here.
Until you run the downloadable verifier, a passing widget means self-consistent and chain-linked — not yet signature-authenticated. The bytes are identical; only the lattice-signature math is deferred.
03The two lanes — v1 shipping, v2 per deployment
Tell the two lanes apart. We name both.
v1 — shipping: the deterministic dual-peer CHSH ritual
Both peers seed a deterministic CHSH ritual computed by SHAKE256 simulation. It is a simulation and the protocol labels it one: its value is that the 623-byte transcript is auditable, chain-linked, and impossible to fabricate after the fact without both seeds — not that qubits were measured.
v2 — in the client, activates per deployment: operator-signed QPU transcripts
The v2 lane binds keys to operator-signed transcripts from real quantum processors. The code path ships in the client and activates per deployment; where it is not active, the v1 ritual carries the binding and this page says so in the present tense.
Downgrade protection
Bell-lane downgrades are signed transparency events, and a session that flips lanes after establishment is hard-rejected in crypto-core. There is no silent substitution: QRNG source fallbacks carry attestation of what actually supplied the entropy.
The deeper physics — entanglement, the CHSH game, why 2√2 — lives on /science and the dedicated instrument site, quantumentanglement.io.
04The record — the questions we get asked hardest
The hard questions.
Why add Bell-binding at all if the hybrid floor already holds?
Because a key-derivation input that any auditor can re-verify — and no classical adversary can precompute — is a different kind of evidence than a hardness assumption. It costs 623 bytes per session and removes nothing: the floor beneath it is unchanged.
Does a simulation add real security?
The v1 ritual adds verifiability, not entropy hardness — the honest claim is auditability of the transcript, and that is the claim we make. Key entropy comes from the hybrid handshake and the QRNG sources, each attested. The v2 QPU lane is where physical measurement enters, and we name it as a separate lane precisely so the two claims never blur.