Transparency & Soundness Report
What verification establishes, the protocol, every stated assumption, and how to verify every pulse yourself.
What verification establishes
Well-formed, signed, chained, and re-verifiable
Verification proves the ledger is well-formed, signed (Ed25519), chained (each pulse commits to the one before it), and that the audited outcomes violate the CHSH inequality on the stated hardware. Every pulse is independently re-verifiable by anyone holding only the public key — no trust in the operator required.
Protocol
| Field | Value |
|---|---|
| Protocol | qbeacon/v3 |
| Genesis | 6544eef49dd317fc97be0ee46355f4f40676e6dccd2be30762d3a8d31e236efd |
| Public key | MCowBQYDK2VwAyEAnTAxkfnLCEzysaa7bU5Vw02UfyPa0C2sVOgQYtHE6UQ= |
| Pairs/pulse | 8192 |
| Challenge | fiat-shamir |
| Signature | Ed25519 |
| Commitment | RFC 6962 Merkle tree |
Assumptions carried by every pulse
These are signed into each pulse record, so they travel with the data.
Verify it yourself
This standalone verifier needs nothing beyond this bundle and Python's standard library plus cryptography — download and run:
curl -s https://qbeacon.ca/historical/pubkey.pem -o pubkey.pem curl -s https://qbeacon.ca/historical/pulses.jsonl -o pulses.jsonl curl -s https://qbeacon.ca/historical/verify.py -o verify.py python3 verify.py pulses.jsonl pubkey.pem 6544eef49dd317fc97be0ee46355f4f40676e6dccd2be30762d3a8d31e236efd
What this standalone tool checks for every pulse: signature, chain, commitment, and (for pulses #0 and #1) the full relay/CHSH recomputation. Pulse #2's CVQC proof is checked with the protocol's verifier-only key.