Automatic & Live Draws Free postal entry — equal chance Provably fair · 18+ · UK only
Open Verification

Draw Verification

Kill Team - Terror On Devlan

Provably fair — cryptographic Draw complete

Draw complete — independently verifiable

This draw used a cryptographic commitment scheme. The draw secret was generated before ticket sales began, its sha256 hash (the commitment hash) was published, and the secret was only revealed after the draw. This proves the winner selection could not have been influenced by ticket sales.

Draw Result

Winner
Winner, Hampshire
Winning ticket
#157
Entries in pool
94 (all entrants)
Winner index
73 (0-based)
Draw executed
22 Sep 2026, 8:31 PM
Entropy source
secrets.SystemRandom (instant-win positions at setup)
Fairness mechanism
SHA-256 commit-reveal — selection by sha256(legion-draw-v1:draw:draw_secret:pool_hash:drand_randomness:counter) rejection sampling

How This Result Was Produced

7 steps, each one checkable against the values published below. Nothing here depends on trusting us — every input is shown.

Verify commitment was published before the draw

This sha256 hash was published when the competition was created. It proves the draw_secret could not have been changed after tickets were sold.

a454b1ee339138c02c7254f77931f6e6fb8ca19d0205556333f2afd766078cd6

Verify the pool-freeze commitment was published before the beacon round

sha256 of the exact UTF-8 string 'legion-draw-v1:pool_freeze:' + pool_hash + ':' + drand_chain_hash + ':' + str(round_number) — colon-separated, no spaces, no trailing newline. Published before the targeted round resolved, it pins both the entry pool and the round while the round's randomness was still unknowable. Rebuild it from this page's published values with the command below.

5821f9812f07f92ba9ca7eba44b266bb93d5b020ff0c77a80de5dc70a5a116fe
python3 -c "import hashlib; print(hashlib.sha256('legion-draw-v1:pool_freeze:22d47de9408cd7c68edf4dfa0162ce4e26b3384989d227dc9e3747e8d4d57fbc:52db9ba70e0cc0f6eaf7803dd07447a1f5477735fd3f661792ba94600c84e971:32434025'.encode()).hexdigest())"

Verify draw_secret matches commitment_hash

The draw_secret is revealed below. sha256(draw_secret) is shown — it must equal the commitment_hash in step 1.

draw_secret (input)

d5e34ff43dd3c2c540190f7acc8fadff40357819f76adb322e3083f9e5384c26

sha256(draw_secret) must equal step 1

a454b1ee339138c02c7254f77931f6e6fb8ca19d0205556333f2afd766078cd6

Verify the entry pool hash

sha256 of every ticket number in the draw pool, in ascending numeric order, joined with commas and no spaces.

22d47de9408cd7c68edf4dfa0162ce4e26b3384989d227dc9e3747e8d4d57fbc

Verify the drand beacon randomness

Round 32434025 of the public drand randomness beacon (chain 52db9ba70e0cc0f6eaf7803dd07447a1f5477735fd3f661792ba94600c84e971). This value is published independently by multiple operators and could not have been known when the pool above was frozen. Check it yourself: fetch https://api.drand.sh/52db9ba70e0cc0f6eaf7803dd07447a1f5477735fd3f661792ba94600c84e971/public/32434025, hex-decode the response's 'signature' field into raw bytes, then compute sha256 of those bytes — it must match the value shown here. (Hashing the ASCII hex text of the signature instead of the decoded bytes gives a different, wrong answer.) The command below does exactly that.

792bd6fd1072a0728607bb17badc703c374eb02d2671977393ebcf943bb40330
python3 -c "import hashlib, json, urllib.request; r = json.load(urllib.request.urlopen('https://api.drand.sh/52db9ba70e0cc0f6eaf7803dd07447a1f5477735fd3f661792ba94600c84e971/public/32434025')); print(hashlib.sha256(bytes.fromhex(r['signature'])).hexdigest())"

Verify the beacon's BLS signature

Before accepting the randomness above, the platform checked drand's BLS12-381 signature for this round against this chain public key — a relay can withhold a round but cannot forge one without drand's private key. Fetch the round's 'signature' field from the URL above and verify e(H(round_bytes), public_key) == e(signature, G2_generator) yourself with any BLS12-381 library; source: https://drand.love/developer/http-api/.

83cf0f2896adee7eb8b5f01fcad3912212c437e0073e911fb90022d3e760183c8c4b450b6a0a6c3ac6a5776a2d1064510d1fec758c921cc22b0e17e63aaf4bcb5ed66304de9cf809bd274ca73bab4af5a6e9c76a4bc09e76eae8991ef5ece45a

Reproduce the winner selection (rejection sampling)

Starting at counter=0, compute sha256(f'legion-draw-v1:draw:{draw_secret}:{pool_hash}:{drand_randomness}:{counter}') as a 256-bit integer. Let limit be the largest multiple of N below 2^256. If the value is >= limit, increment counter and retry. Otherwise winner_index = value mod N.

counter=0, winner_index=73

Check It Yourself

Run every check in your own browser. It recomputes the hashes and the winner selection locally from the values published on this page, and fetches the drand round directly from the public relays — nothing is sent to our servers, so a pass cannot depend on trusting us.

  1. Confirm sha256(draw_secret) equals the commitment hash in step 1.
  2. Confirm the sha256 of the entry pool below equals the pool hash in step 3. Hash the text exactly as shown — ticket numbers in ascending numeric order, separated by commas, with no spaces and no trailing newline.

    Entry pool — ticket numbers in ascending numeric order

    2,3,5,6,10,13,15,18,21,22,31,32,33,34,35,36,38,41,43,44,45,46,47,48,49,52,53,56,58,59,61,66,67,68,71,73,75,77,78,79,85,87,93,94,95,98,100,105,107,109,110,111,112,114,117,118,119,121,122,123,125,127,128,131,133,134,135,137,143,144,147,151,154,157,158,159,160,165,167,172,173,175,179,182,184,186,187,190,191,193,194,195,196,199
  3. Run the pre-filled command below to reproduce the beacon-seeded rejection-sampling winner index (counter=?, expected winner_index=73). This folds in the drand beacon randomness from the step above alongside the draw secret and pool hash, so the winner could not have been known until that round resolved.
    python3 - <<'PY'
    import hashlib
    draw_secret = 'd5e34ff43dd3c2c540190f7acc8fadff40357819f76adb322e3083f9e5384c26'
    pool_hash = '22d47de9408cd7c68edf4dfa0162ce4e26b3384989d227dc9e3747e8d4d57fbc'
    beacon_randomness = '792bd6fd1072a0728607bb17badc703c374eb02d2671977393ebcf943bb40330'
    total_entries = 94
    counter = 0
    limit = (1 << 256) - ((1 << 256) % total_entries)
    while True:
        seed = hashlib.sha256(f'legion-draw-v1:draw:{draw_secret}:{pool_hash}:{beacon_randomness}:{counter}'.encode()).digest()
        candidate = int.from_bytes(seed[:32], 'big')
        if candidate < limit:
            print(f'counter={counter} winner_index={candidate % total_entries}')
            break
        counter += 1
    PY

Full Entry List

All sold tickets with entry method and optional-question answer status (no personal names). Download it to cross-reference ticket numbers against the draw pool; the "In Main Draw" column marks which rows formed it.

Download entry list CSV

Independent Timestamp Proof

Each commitment hash is anchored to the Bitcoin blockchain via OpenTimestamps. A confirmed proof establishes the hash existed before the Bitcoin block that attests it — checkable without trusting our records. Save the commitment hash to a file and check the proof with the free ots tool: printf '%s' 'COMMITMENT_HASH' > commitment.txt && ots verify -f commitment.txt proof.ots

Draw commitment — anchored in Bitcoin 8 Sep 2026 17:04 UTC

a454b1ee339138c02c7254f77931f6e6fb8ca19d0205556333f2afd766078cd6 Download OTS proof

Instant win commitment — anchored in Bitcoin 8 Sep 2026 17:04 UTC

09d6b0545e132ec3789c1f752fbbce432246bdcdbe5e27275444a323512e6ac9 Download OTS proof

Pool freeze commitment — anchored in Bitcoin 22 Sep 2026 22:04 UTC

5821f9812f07f92ba9ca7eba44b266bb93d5b020ff0c77a80de5dc70a5a116fe

What this proof does and does not show: Bitcoin confirmation takes hours, while the targeted drand round resolves seconds after the pool freeze — so a confirmed proof here demonstrates the pool-freeze commitment existed before its attesting block, not that the freeze happened before the drand round. The freeze-before-round ordering rests on the commitment having been published before the round resolved (step 2 above) and on our audit records.

Download OTS proof