/clussy/GIVEAWAY #14

THE DRAW IS DONE

Clussy #0499

closed Tue 25 Aug, 19:50 UTC with 26 in the hat.

Clussy #0499
COMMON

one of 1,111 · #0499

see its traits →

26entered

closed

opened Tue 25 Augwas due Tue 25 Aug, 19:50 UTC

the winner

@naneksun

going to 3U6n…E3g4

how it was drawn
  • entries in the hat26
  • dropped, post deleted0
  • dropped, never posted3
  • dropped, not their post0
  • seedsolana blockhash
  • slot441,702,882

EKXRPQnwSV1tN1w8ciiVgaMz3SUP8sH8SGZYthho1Mce

take the seed above, add :14:296,297,298,300,301,302,303,304,305,306,307,309,310,311,312,313,314,315,316,318,319,320,321,322,323,324 to the end of it, sha256 the lot, read the first 16 bytes as a number, and take it modulo 26 — that is the position in the list above. the numbers are entry ids and name nobody.

one entry per X account, per wallet, per post. a post that is taken down before the draw takes its entry with it — that is the whole deal. the winner is picked from a Solana blockhash read at the moment of the draw, and the hash is published below it so the pick can be repeated by anyone who wants to check.

12 GIVEN AWAYtap one for the receipt

the last dozen. older draws keep their own pages.

how every one of them was picked
  1. entries lock the moment the giveaway’s clock runs out. nothing goes in after.
  2. every post is checked again. deleted, never posted, or not yours — the entry drops out. a post nobody could reach stays in; nobody is disqualified on a maybe.
  3. a Solana blockhash is read at that instant and published with its slot. nobody here chooses it and nobody knew it when they entered.
  4. the surviving entry ids are hashed in the published order:

sha256(seed:giveaway id:pool) → first 16 bytes as a number → mod pool size

that number is the position in the pool, and the entry at it is the winner. the seed, the slot and the pool are all published, so the arithmetic is one shell command and no trust. every draw’s own numbers are on its plaque.

MINT ONE — 0.1749 SOLthe rest of the thread →