Drand Quicknet · Verifiably Fair
Every draw can be checked against the public drand beacon and recomputed in your own browser — no trust in our servers required.
Have your verification key ready — it is shown with every draw result and never expires.
1
Enter your key
Paste the verification key below to load the complete draw record — every seed, hash, parameter and the committed drand round.
2
Check the beacon
Follow the direct links to Cloudflare’s relay and independent drand relays. The server seed must equal the published randomness for that round — we can’t fake it.
3
Recompute the result
One click reruns the whole HMAC-SHA256 calculation in your own browser with the Web Crypto API — or reproduce it by hand with our open scripts.
Verify a Draw
Enter a verification key to load the full draw record. Verification runs automatically in your own browser.
Draw Details Drand Quicknet
Round ID:
✓ Verified by the Drand distributed randomness beacon
Derived Numbers
Every 4-byte read of the hash, in order. Rejection sampling guarantees uniform probability.
| Attempt | Value (uint32 LE) | Ticket | Outcome |
|---|
Verifiably Fair Data
All Together
Pre-hash string — the combination of all the above data, provided to HMAC-SHA256 with the Server Seed as the key:
Combined as: client_seed:round_id:static_salt:tickets_sold:max_tickets
Verification
Calculation log
Prefer to check by hand? Use the scripts on the Manual Verification page with the data shown here.
Drand Proof
This draw was generated with the Drand Quicknet beacon, run by the League of Entropy.
Draw Information
Draw Timeline
What the draw record contains
Server Seed
The randomness published by the drand network for the committed round. It’s generated by the League of Entropy — not by us — and must match the beacon on every independent relay.
Client Seed
The exact millisecond timestamp assigned by the server the moment the draw was started. Forcing the timestamp means the outcome can’t be cherry-picked in advance.
Round ID & Static Salt
The draw’s unique UUID plus our published salt. Both are fixed inputs to the hash, making every draw’s calculation unique and reproducible.
Tickets Sold & Max Tickets
The competition parameters entered at draw time. Max Tickets sets the range — the winning ticket is always between 1 and Max Tickets, with every number equally likely.
Combined Hash
HMAC-SHA256 of all the inputs above, keyed with the server seed. The winning ticket is derived from this hash by rejection sampling — uniform probability, zero modulo bias.
Record Hash
Every completed draw is SHA-256 hashed and chained to the previous record. Altering or deleting any historical draw breaks the chain and is immediately detectable.
Want to go deeper?
Reproduce any result by hand with open PHP and JavaScript scripts, learn how the drand beacon works, or read exactly how we guarantee fairness.