How this draw is provable

Before entries closed we published a commitment: a one-way fingerprint (SHA-256) of a secret random seed. After the draw we revealed the seed. Because the commitment was public before entries closed, the seed could not have been changed afterwards to draw a particular ticket.

The draw also folds in a public randomness beacon (drand, the League of Entropy) whose value is only published after entries close. Anyone can re-fetch the exact beacon round below and confirm the same value went into the draw.

Commitment (published before entries closed)

fc97333e91134efac0548917f77426335129f7d8bdfa13bf9b39eb566b744683

Revealed seed (published after the draw)

48b29f72e3e9f8ba99dc37255db6f5379ffbb32261cf77e32030066bb1934cf4

Beacon round (emitted after close) & its public value

Round 6,474,747 on the drand chain 8990e7a9aaed2ffed73dbd7092123d6f289930540d7651336225dc172e51b2ce

d1d6079eb18fc5509ba73e62defbc7a46b656668d8b7036a019bbf5803c078d6

Re-fetch it: curl https://api.drand.sh/8990e7a9aaed2ffed73dbd7092123d6f289930540d7651336225dc172e51b2ce/public/6474747

Check it yourself

1. The seed matches the commitment

Run SHA-256 on the revealed seed - it equals the commitment above. For example, in a terminal:

printf '%s' '48b29f72e3e9f8ba99dc37255db6f5379ffbb32261cf77e32030066bb1934cf4' | sha256sum

2. The seed and the beacon draw the winning ticket number

Every one of the 44 tickets (numbered 1 to 44) went into this draw. The winner is drawn from the locked-in seed mixed with the post-close beacon value shown above - both are in the $msg below. The seed was committed before entries closed, and the public beacon that decides the winner didn't exist until after - so the result couldn't be set in advance or predicted. Recompute it and you'll get ticket #32:

$seed  = '48b29f72e3e9f8ba99dc37255db6f5379ffbb32261cf77e32030066bb1934cf4';
$total = 44;                       // tickets in the draw (numbers 1..44)
$msg   = 'draw:01a08a73-0c92-728d-aba9-bade694a16db:'.$total.':d1d6079eb18fc5509ba73e62defbc7a46b656668d8b7036a019bbf5803c078d6';   // note: the trailing value is the drand beacon above
$span  = 1 << 60;                          // 60-bit space
$limit = intdiv($span, $total) * $total;   // reject above this to remove bias
$i = 0;
do {
    $n = (int) hexdec(substr(hash_hmac('sha256', $msg.':'.$i, $seed), 0, 15));
    $i++;
} while ($n >= $limit);
echo ($n % $total) + 1;                     // => winning ticket #32

3. Ticket #32 belongs to the winner

That ticket number is held by exactly one entry - Amy M. from Inverness. We publish a fingerprint of every ticket number in the draw, so the set of numbers can't be altered after the fact, and we hold the full list in our tamper-evident audit trail, available to the Advertising Standards Authority on request.

Ticket-numbers fingerprint

7d7caccb8ac52296c9cd2f7975056dcd30885d47fa81ff5201c67b6fcafb4555

How ticket numbers are assigned

On this competition you don’t choose your ticket number, and it isn’t simply the next number in order. When you buy, the system gives you a number using a secret shuffle that was set when the competition opened, before anyone had bought a ticket, and can’t be changed after.

Because that shuffle is secret and gives everyone a different number:

• Two people can never end up with the same number.
• Nobody, not you and not us, can guess which number a purchase will get. On this draw the number itself isn’t what picks the winner - that’s the draw above, which nobody can predict.
• Your number is fixed the instant you buy, and recorded straight away.

We keep the shuffle secret so no one can work out in advance which number a purchase will get, which is what stops anyone targeting a winning ticket. Every number that’s given out still appears in the competition’s entrants list, so the numbers in play are public and can’t be quietly changed later.

You can see them: every entry and its ticket number is listed on the competition’s entrants page.

// 1. the key matches the fingerprint published at open:
printf '%s' 'rLKXjKqT6XtCsoMo4C6GNNkzNiGL8vgTWR9ZKVI6' | sha256sum        // => d19f69b01b2d955b530e2b82dd262ad3090cc62b88bad890d7b6eaf0b70ea95d

// 2. re-run the shuffle: position -> ticket number
$seed   = 'rLKXjKqT6XtCsoMo4C6GNNkzNiGL8vgTWR9ZKVI6';
$domain = 44;   // the pool the numbers are shuffled within
$prf = fn($v,$r) => (int) hexdec(substr(hash('sha256', "$seed:$r:$v"), 0, 8));
$permute = function(int $pos) use ($domain, $prf) {
    $half = (int) ceil(((int) ceil(log($domain, 2))) / 2);
    $mask = (1 << $half) - 1;
    $x = $pos - 1;
    do {
        $l = ($x >> $half) & $mask; $r = $x & $mask;
        for ($i = 0; $i < 4; $i++) { $n = $l ^ ($prf($r, $i) & $mask); $l = $r; $r = $n; }
        $x = ($l << $half) | $r;
    } while ($x >= $domain);
    return $x + 1;
};
// $permute(1), $permute(2), ... are the ticket numbers, in the order they were issued.