Staging 25 Oct 21:13 — Sequential
Draw verification, recomputed from published evidence every time this page is loaded.
Checked in your browser
nothing below is taken from our answerChecking…
Your browser is recomputing this draw from the published evidence.
-
…
Receipt matches its published fingerprintwaiting
-
…
Entry list downloaded and hashed in your browserwaiting
-
…
Randomness fetched directly from drandwaiting
-
…
Winner recomputed from those two inputswaiting
This runs entirely in your browser —
read the code.
The randomness is fetched from drand's own servers, so we are not in that request path.
The one thing your browser cannot establish alone is that this entry list is the one that
existed before the draw. That is what the
external timestamp
from rfc3161 proves — check it offline with
openssl ts -verify.
Result
#6 winning ticket
| Valid tickets in the draw | 15 |
|---|---|
| Numbers drawn | 1 drawn from the range 1–15, 0 skipped as unsold |
| The draw, in order | #6 sold, wins These are not separate draws. One round of public randomness produces one seed, and that seed produces this exact sequence in this exact order — so nobody could stop earlier, carry on further, or run it again for a different answer. |
| Entries closed | Sun, Oct 25, 2026 9:44 PM UTC |
| Drawn | Sun, Oct 25, 2026 9:46 PM UTC |
Times here are UTC, deliberately. They are meant to be checked against things outside this site — openssl ts -verify prints the timestamp token in UTC, and drand's round schedule is UTC — so showing them in local time would make this page disagree with the very evidence it invites you to check it against.
The ordering this rests on
The entry list was sealed before the number that chose the winner existed.
Our clock is on neither side of this. The left time is certified by a timestamping authority with no relationship to us; the right is computed from drand's genesis and period, which anyone can do from public parameters.
Our own re-check
PASS
Our server also recomputed this draw from its original evidence just now, and the result matches. You should not need to take our word for it — the check above is the one that counts.
Verification checks
- PASS Receipt integrity sha256 c23a79179235b50eb223994cc718bb40b17ba1094f075e0995b5426ad000a441 (unsigned)
- PASS Algorithm supported winner-selector-v1 / drng-v1, frozen vectors reproduce
- PASS Snapshot integrity 15 rows, sha256 0682aa7270419423715a4d13840cecdc27be6eeff594fb9f1e50c370e51003b6
- PASS Commitment timing anchored 2026-10-25T21:44:03Z, before round 33387133 at 2026-10-25T21:46:03Z
- PASS Randomness round 33387133 on 52db9ba70e0cc0f6eaf7803dd07447a1f5477735fd3f661792ba94600c84e971 verified against the chain public key
- PASS Audit chain 43 events, hash chain intact, 2 externally timestamped head(s) match
- PASS Winner recomputed 1 drawn number over range 1-15, 0 skipped as unsold, winner ticket 6
How this draw worked
One winning ticket, drawn from a public randomness beacon nobody controls.
- When entries closed, every valid ticket was written to a single list in a fixed order, and that list was fingerprinted (SHA-256). Paid and free entries are in the same list, allocated by the same process.
- That fingerprint was timestamped by an external service before the random number used to pick the winner existed. So the entry list could not be changed afterwards to suit the result.
- The random number came from drand, a public randomness beacon run by an independent group of organisations. The exact round was named in advance, and its cryptographic signature is checked here — not merely trusted.
- The entry list fingerprint and the random number were combined to produce one position in the list. Ticket 6 was at that position.
Because every input was fixed before the randomness was known, and every input is published below, anyone can repeat this calculation and get the same answer. Nobody at Draw Engine (staging) could have chosen the outcome.
The exact inputs
| Competition ID | 01M5TEJPGN5ZDKFDXKVERGC8AC |
|---|---|
| Jurisdiction | GB |
| Terms version | 2026-10 |
| Entry list fingerprint | 0682aa7270419423715a4d13840cecdc27be6eeff594fb9f1e50c370e51003b6 |
| Entry list format | snapshot-v1 |
| Fingerprint timestamped | Sun, Oct 25, 2026 9:44 PM UTC · rfc3161 |
| Randomness network | drand · 52db9ba70e0cc0f6eaf7803dd07447a1f5477735fd3f661792ba94600c84e971 |
| Signature scheme | bls-unchained-g1-rfc9380 |
| Round | 33387133 |
| Randomness | 985d54abc7bb01f4be7aa80e2fa09ee926ef4979ad97220a9a884acce9346f44 |
| Round signature | b1f9f43d4c3d7eadae09780e4e006c2578bc966f0cce362332d6e9a3fc301fe8ab7a4f8bf1b2295b26174ed1b8035236 |
| Chain public key | 83cf0f2896adee7eb8b5f01fcad3912212c437e0073e911fb90022d3e760183c8c4b450b6a0a6c3ac6a5776a2d1064510d1fec758c921cc22b0e17e63aaf4bcb5ed66304de9cf809bd274ca73bab4af5a6e9c76a4bc09e76eae8991ef5ece45a |
| Algorithm | winner-selector-v1 / drng-v1 |
| Receipt fingerprint | c23a79179235b50eb223994cc718bb40b17ba1094f075e0995b5426ad000a441 |
| Seed, derived in your browser | not yet computed |
The verification package contains the entry list, the randomness proof, the receipt and a full specification of the algorithms, so the result can be reproduced with no access to our systems. It contains no personal data: entries appear only as opaque identifiers.
Check the rest of this competition
Entry list
Every ticket in this draw
Search for your own number or entry reference.
Public ledger
Every published draw
Hosted outside the operator's infrastructure.
New to this? How the draw is made checkable · Verify it from a command line · About the drand beacon