QBEACON

Randomness you don't have to believe in.

Connecting…
Current Pulse
Loading...
ID: --- • AGE 0s
Verify Soundness Explore Ledger
---
Output width (this pulse)
Live
Continuous cadence
Ed25519
Pulse signatures
---
Live source

Current Pulse Evidence

One record. Three checks.

Published record · server verification
Bell Violation (S)
Loading...
Awaiting pulse verification
Pulse Commitment
Loading...
Published record commitment
Signature
Loading...
Server-reported Ed25519 check
This pulse, in detail
Loading...
Output diagnostics — rolling window

These checks describe the published stream, not its physical origin. Across the last 1000 pulses:

—
Bias (R_raw)
—
128-bit block repeats
—
Compression ratio

Loading live statistics…


Build with QBeacon

One public pulse. Many applications.

Signed records for your application. Future-pulse selections in development.

Developer quickstart → Open console → Evidence and assumptions →

Quantum Verification

Hardware produces the evidence. QBeacon verifies and attests.

  1. 01MeasureHardware record
  2. 02RecomputeIndependent calculation
  3. 03AttestSigned receipt + limits
Bell / CHSH · testable

Bell-test verification

Measurement counts in. Recomputed CHSH statistic and a signed receipt out.

Inspect archived experiments →

Record verification does not establish a loophole-free Bell test.

Product 02 · active research

CVQC / LWE verification

A second path: classical challenges to a quantum prover, under LWE assumptions.

Protocol research →

Experimental. Not a production Mahadev proof.

On-Chain Oracle

Base Mainnet · separate from the beacon

Inspect QBeaconOracleCore directly. The explorer shows its current state.

Deployment details
Deployment reference
Base
Network · chain 8453
#11777
First pulse anchored · 2026-09-03
0.00067878
Protocol fee · ETH per call
Contract Address
0xD8AC8a35C9A53C9078450ff1a2a7209cbd6e34d0

View contract on BaseScan →  ·  BaseScan is authoritative for current on-chain state, including the latest anchored pulse.


Public Ledger

Historical Record

Loading...
Pulse # Random Output (first 16 bytes) Commitment Status
Loading ledger...

How QBeacon Works

Signed, chained, independently verifiable randomness

  1. 01SourceProvenance per pulse
  2. 02Sign + chainEd25519 + commitments
  3. 03PublishPublic record + verifier
Technical overview

Public randomness you can verify, not just trust

QBEACON publishes public, timestamped, signed random values linked to preceding records. Signatures and chain commitments make changes detectable against previously retained records; they do not by themselves prevent an operator from presenting an alternative history.

Each pulse is signed with an Ed25519 key and carries a Merkle commitment, so anyone can independently re-verify the entire chain without trusting the operator. Relay sources are identified on each pulse: drand provides distributed threshold-signature randomness; ANU QRNG provides quantum-optical randomness. They are different sources with different assumptions. Bell-test pulses bind a value to a CHSH measurement on IBM quantum hardware. Every pulse's device_class and caveat fields state exactly what it rests on.

CVQC / Mahadev is a separate research direction based on computational assumptions, including LWE hardness. Our experimental work is not a production-complete implementation.

How it works, step by step

1. Entropy collection. The source recorded on each pulse supplies the input. A drand relay, an ANU quantum-optical relay, and a Bell experiment have different provenance; output statistics do not establish that provenance.

2. Signing & chaining. The new value is signed with the beacon's Ed25519 private key and chained to the hash of the previous pulse, so the ledger is tamper-evident.

3. Publication. Each signed pulse is published to the public ledger as it is produced, along with its Merkle root and device-class caveat.

4. Independent verification. Download records and the standalone verifier to recompute signatures, commitments, and any supplied Bell statistics. Pin a trusted public key. Physical-source provenance and experimental assumptions remain separate checks.

Real-world use cases

Lottery & gaming fairness

Provably fair draws, raffles, and game outcomes — auditable by every participant.

Audit sampling

Regulators select random samples or test cases transparently and reproducibly.

Distributed consensus

A common, unpredictable input for leader election and shard assignment.

Public challenges

Shared inputs for protocols designed for public randomness. Never use public pulses as secret keys.

Academic research

A reproducible public data source for studying randomness and quantum info.

Frequently asked questions

What is a randomness beacon?

A service that publishes fresh, signed random values on a regular cadence, so anyone can use and verify them. QBEACON publishes continuously; every pulse and its exact timestamp are in the public ledger.

How is QBEACON different from other randomness sources?

Most RNGs are opaque — you must trust the provider. QBEACON's output is signed, chained, and independently re-verifiable by anyone, with every soundness assumption stated openly rather than hidden.

Can I use QBEACON values in my application?

Yes. The public ledger and API are freely accessible. The /ledger endpoint returns the full signed chain, and /pulses/latest returns the most recent value.

How often are new values published?

The target cadence is 65 seconds. The pulse timestamp shows actual freshness; interruptions can delay publication.

What does "independently re-verifiable" mean?

You can download the ledger, public key, and verifier script and recompute every signature, chain hash, and Bell statistic yourself — without trusting the operator or this website.

What cryptographic signatures are used?

Ed25519, with Merkle-tree commitments for the chain. The standalone verifier needs only Python's standard library plus the cryptography package.