ENTANGLEMENT
IS THE
DESTINATION.
QERYX is the first messenger on a trajectory to real quantum-entanglement communication — a channel where interception is not merely infeasible but physically detectable. Today, that means every session key is anchored to a signed, verifiable Bell-measurement pulse, layered above a hybrid X25519 + ML-KEM-1024 floor with ML-DSA-87 signatures. Everything on this page is labeled by what it actually is.
Break the classical bound with your own hands
This is a live CHSH experiment running in your browser. Photon pairs leave the source; you choose the detector angles. A local hidden-variable source — any classical explanation of reality — can never push the correlation score S past 2. An entangled source reaches 2√2 ≈ 2.828. That single fact is what this entire project is built on.
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 — the bundled sample says
local-sim, and the verifier shows it. When hardware pulses ship, that label is how
you will know.
Recompute a signed beacon pulse in your browser
No trust in QERYX required. Your browser fetches one pulse, recomputes its SHA3-256 self-commitment from the raw bytes, checks the hash-chain link to the previous pulse, and re-derives the CHSH Bell-violation flag exactly as the signer did. Nothing here calls home; the code is verify.js and sha3.js — a few hundred readable lines in total.
Checked live, in this browser
- SHA3-256 self-commitment.
pulse_hash = SHA3-256(canonical(record) ‖ signature)recomputed from the wire bytes and compared to the value the pulse carries. - Hash-chain link.
record.prev_hashcompared to the previous pulse’s hash — the chain is append-only. - CHSH violation flag. Re-derived as
S − 3σ > 2.0and checked against the signed flag;Sis shown against the Tsirelson bound 2√2 ≈ 2.828. - Canonical encoding. Number literals preserved verbatim (
0.0stays0.0), keys sorted, no whitespace — byte-identical to the signer.
Offered as a downloadable verifier
- ML-DSA-87 signature (FIPS 204). The lattice signature over the exact same canonical bytes. In-browser ML-DSA-87 verification is heavy (large keys, NTT-domain arithmetic), so we keep this widget small and ship the full check as a standalone verifier you run locally.
- Beacon public-key pin. The verifier confirms the signing key matches the out-of-band fingerprint
e7223f32…3708de3f. - Entropy-extractor accounting. Re-runs the min-entropy estimate and Toeplitz output-length rule the pulse claims.
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.
Watch the loophole-free anchor, live
R2 — BEING WIRED INCURBy — the public Bell-test randomness beacon from NIST and the University of Colorado Boulder — publishes loophole-free entanglement measurements on a public, hash-chained feed. It is the anchor QERYX is wiring in next. Shown here live for transparency; not yet folded into shipped keys.
How a Bell-measurement reaches your session key
Measure
A quantum source is prepared in a Bell state and measured under four CHSH setting pairs. The correlation sum S is computed; the ideal quantum maximum is the Tsirelson bound 2√2 ≈ 2.828, and the classical ceiling is 2.
Extract
Raw measurement bits pass a conservative min-entropy estimate (a tested subset of NIST SP 800-90B — not the full battery, not CMVP-validated) and a Toeplitz strong extractor, yielding the published output.
Sign & chain
The full record — S, sigma, the violation flag, entropy accounting, and output — is signed with ML-DSA-87 (FIPS 204) and self-committed as pulse_hash = SHA3-256(canonical(record) ‖ signature), with prev_hash linking the previous pulse into an append-only chain.
Verify
The app re-checks every invariant against a pinned public-key fingerprint (never a key carried inside the pulse), failing closed on anything malformed. The widget above performs the hash, chain, and flag checks live; the signature check ships as a downloadable verifier.
Fold — additively, never below the floor
The verified pulse is mixed into the QSEED through the same multi-source path as the device’s own quantum samples, via XOR + HKDF-Extract over a superset of inputs. Extracting over more named sources can only raise the adversary’s uncertainty, never lower it. The pulse hash is also bound into the session context, so the key depends on which pulse was folded — while the device’s own entropy floor (its quantum samples or OS RNG) is always present underneath. A missing, offline, or rejected pulse degrades cleanly to that floor.
The ladder to real entanglement communication
Early AI was real, and honestly the first step on a long trajectory — nobody needed it to be the destination to matter. Same discipline here: we claim 100% of what is true at each rung, label the rest, and ship a rung only when it is real. Honest status labels are the moat.
-
R1SHIPPING
Own-beacon Bell-measurement bound into keys
A QERYX-run quantum source runs a CHSH test; a signed, hash-chained pulse (ML-DSA-87 + SHA3-256) carries the result and extracted output. The app verifies the pulse and folds it into the QSEED as an additive public co-factor. S > 2 here is a device-behaviour check under trusted-device assumptions — the locality and detection loopholes are open, so this is evidence the device behaved as a quantum source, not a loophole-free entanglement proof.
-
R2IN PROGRESS
External loophole-free anchor via CURBy
Bind the loophole-free public Bell-test beacon (CURBy, NIST + CU Boulder) alongside the own-beacon pulse, so the co-factor inherits a measurement where the locality and detection loopholes are closed. The pulse-fold path is built; wiring CURBy’s format and pin — and proving the end-to-end fold in the shipping clients — is the remaining work. You can watch the anchor live in the section above.
-
R3ROADMAP
Beacon quorum + public transparency log
Require agreement across jurisdiction- and vendor-diverse beacons before a pulse is counted, and gossip the pulse chain to independent witnesses who co-sign what they saw — so no single operator can steer the co-factor, and a forked or withheld history is detectable by anyone.
-
R4RESEARCH
Our own measured entanglement; entanglement-distributed links
Running CHSH tests on cloud quantum processors we operate ourselves — labeled an on-chip entanglement witness, because a same-chip test is never loophole-free and we will not call it device-independent. In parallel: entanglement-distributed keys for fixed, high-value server links over metro fiber and satellite quantum networks, where the hardware already exists.
-
R∞HORIZON
Q-Entangle-Absolute — device-to-device entanglement
The summit: two endpoints run a loophole-free Bell test between them over a quantum network. The shared key is measured from entanglement only they hold, seeded above the post-quantum floor. The property nothing classical can offer: by the monogamy of entanglement and the no-cloning theorem, an eavesdropper must disturb the state — S drops measurably below the Tsirelson bound, and a full intercept collapses it to the classical ceiling of 2. The channel itself reports the intrusion. Interception stops being a secret.
This does not exist for phones today, and we never claim two phones share entanglement. But every component already exists in a lab: loophole-free Bell tests, metro-scale entanglement swapping, satellite distribution over 1,200 km, device-independent QKD over meters. The gap is miniaturization, integration, and network engineering — the same kind of gap computing itself once crossed.
The quantum layer rides above this. Never instead of it.
Confidentiality never depends on the quantum layer. It is an additive, public co-factor: it can raise an adversary’s uncertainty, it can never lower yours. Offline, keys rest on the device’s own quantum/OS entropy floor.
What this is — and is not
- Is: the first shipping messenger to fold a verified, signed quantum Bell-measurement into key derivation, above an X25519 + ML-KEM-1024 hybrid floor with ML-DSA-87 signatures.
- Is not: quantum key distribution, quantum teleportation, quantum networking, or two phones sharing entanglement. Those do not exist for phones today; we make no such claim.
- The honest boundary on R1: the own-beacon CHSH test is a device-behaviour check (locality and detection loopholes open). The loophole-free anchor comes from CURBy (R2). The co-factor is additive and public — it steers the seed, it never is the secret.
Build this with us
The summit needs integrated photonics, quantum networking, and DIQKD people — and it needs cryptographers who enjoy breaking things more than believing in them. If the honesty labels on this page made you trust us more, you are exactly who we want reviewing the spec.