@my•••••••••oOrganiserDrawn · verified
Get new Subscribers
Result5 winners · 4 of 5 deliveredDrawn Oct 29, 22:02 UTC
Timeline
- Commitment publishedOct 22, 23:00 UTCHash of the secret seed: 65c87b79472431a8… — published before the first entry existed.
- Entries closedOct 29, 22:00 UTC11 entries counted · 0 filtered as likely bots.
- DrawnOct 29, 22:02 UTCTON block #102162666 · 5 winners.
- Prizes deliveredOct 29, 22:03 UTC4 of 5 delivered · 1 could not be delivered.
Recompute it yourself.
Commitment
65c87b79472431a83882579ec2f1e6ac1bcd73b11085ee417ed6a7878119d9f7
Published when the giveaway opened — before anyone had entered, and before the seed below existed in public.Entrant list hash
be96095a4f80df0df38cfa479375f2ece471cccb2bdbdd59d5d9ea6bedcf03f9
Published when entries closed — before the seed was revealed, so the entrant set could not be edited to fit the result.TON block
#102162666tonviewer ↗
Randomness from a masterchain block produced after entries closed. Nobody can predict or influence it.Block hash
9a6e5bc6ee8c6b396888dca576a3275bcf3b43a36cf00f6cd69c67343997fbf5
The block's own root hash, as any TON node reports it.Revealed seed
ee9d0e0c01ba26984aa35c122a85e567389e88a4df9701e6b78f43b5d8dbbcd3
Revealed after the draw. Its sha256 is the commitment in the first row — check that yourself.Final seed
d2e0debfbcca34948ea03f47d6038472ace8a94c0c5ccf48af302b8c55583dba
What the winners were actually drawn from.Algorithm
pf-2
A change to any rule below is a new version, never an edit to this one.How it is derived
final_seed = sha256(server_seed ‖ block_hash ‖ entrants_root)winner i = pool[ HMAC-SHA256(final_seed, "winner:i") mod n ]
All three inputs are mixed as raw bytes, in that order. The pool is every entrant in the published list, ordered by entry ID; n is how many are left in it, because winners are drawn without replacement — each pick is removed before the next one is derived. The index uses rejection sampling: a digest at or above the largest exact multiple of n is discarded and re-derived from "winner:i:retry:k", so no entry is favoured by the remainder.- Anti-bot: shadow mode — likely bots are flagged, no one is removed.
Winners
- 0155565cee…3462entry ID 73Gift · 15 StarsDeliveredDelivered in Telegram
- 02bbc35721…2be3entry ID 80Gift · 15 StarsDeliveredDelivered in Telegram
- 030ee07c61…949aentry ID 76Gift · 15 StarsCould not deliver
- 04f33afab8…6107entry ID 75Gift · 15 StarsDeliveredDelivered in Telegram
- 05a7610f78…c8a7entry ID 83Gift · 15 StarsDeliveredDelivered in Telegram
Check it yourself
You do not have to trust the button above. Everything is published:
- the draw record (JSON)
- the entrant list (11 lines, pseudonymous)
- the verifier source
- TON block #102162666 on an independent explorer
Draw verified by MyStars. This page proves this particular draw was fair; it is not a judgement about the channel that ran it.
Names are hashed. Yours is findable.
Every line is sha256 of your Telegram id and a salt shown only to you, so the list cannot be read backwards into names — not by a stranger, and not by us. Paste the hash the app gave you; the match runs in your browser against the list linked here.
11 entries · sorted by entry IDDownload the list ↓plain text, one line per entry
IDHash
- 7355565cee…3462Winner
- 75f33afab8…6107Winner
- 760ee07c61…949aWinner
- 775cfd83e0…6a7a
- 79ff07044f…c5c5
- 80bbc35721…2be3Winner
- 81bbfaeb4e…0213
- 83a7610f78…c8a7Winner
Entrants are listed by a salted hash, never by name or Telegram id; winners are shown with their id masked. Only the organiser sees who is behind each entry.