QBEACON LIVE
Connecting to the beacon

Watch randomness
being made — then
check it yourself.

Every pulse identifies its own source, is signed, and is chained to the one before it. This page follows each pulse as it lands and re-checks the signature and chain in your own browser.

Latest pulseReading source…
#—
published —
checking…
Output R—
Signature
Ed25519
Output
4,096 bits
Pulses on chain
—
Avg spacing
—
01 · Live pipeline

How a pulse is born

When a new pulse arrives it is replayed here, stage by stage, using its real published values.

01
Declared source
waiting…
Read from this pulse's signed device class and caveat.
02
Extract
—
Toeplitz extractor condenses it into R.
03
Chain
—
Commits to the previous pulse's hash.
04
Sign
—
Ed25519, with the beacon's published key.
05
Publish
—
On the public ledger for anyone to check.
02 · The chain

Verified by your browser

A green link means your browser recomputed the previous pulse's hash and it matches. Select a block to inspect it.

03 · Don't trust — verify

Check it yourself

Pick a block above, or wait for the next pulse.

    Uses the public key from /pubkey and the pulse JSON from /pulses/{id}. The same checks run offline with verify.py.

    The 4,096 bits

    One pixel per output bit of the selected pulse.

    Ones—
    Longest run—
    04 · Use it

    Fair tools from the latest pulse

    Recomputable by anyone: SHA-256(tag ‖ R ‖ tool ‖ input ‖ counter) with unbiased rejection sampling. Same pulse, same input — same answer.

    Coin flip

    ?

    Dice

    ?

    Pick a number

    ?

    Shuffle a list

    For fun and demos. For a real giveaway with a sealed entrant list and a signed certificate, use QBEACON Draws — a result picked here could be retried on a later pulse, which a sealed draw prevents.