drand, explained without the maths
The public randomness beacon, in plain words
A randomness beacon is a public service that publishes a fresh random number at fixed times, signed so anyone can check it. PickFaire uses drand: after your entry list is locked, the next round's number picks the winners.
Three things to know
It is public
drand's "quicknet" chain publishes a new random value every 3 seconds, and anyone can fetch any round from several independent relays. Nobody has to trust our copy.
Nobody can choose it
Each value is produced jointly by a network of independent organisations, the League of Entropy. No single member, and not us, can know or steer a round before enough members sign it.
It comes after the lock
The round is fixed at the moment you lock the entry list: the first one published at least 20 seconds later. The list is public before the number exists, so the number cannot be picked to suit the list.
An analogy
Imagine writing the entrants' names in a sealed, numbered order, posting a photo of the sealed envelope, and then agreeing that the winner is decided by the closing figure of tomorrow's lottery draw. Nobody can change the envelope without the photo giving it away, and nobody controls the lottery. A beacon draw is the same idea, made exact: the "envelope" is the SHA-256 hash of the locked list, the "lottery" is a drand round, and a published formula turns the two into the winners.
What happens to the number
- The round's signature is published by drand. Its randomness is SHA-256 of that signature: 32 bytes.
- A seed is computed from that randomness, the hash of your locked list, the draw code and the draw number on the post (HMAC-SHA256).
- The seed drives a shuffle of the locked list. The first people in the shuffled list are the winners, the next ones the backups.
Every step is deterministic: the same round and the same list always give the same winners. The exact formulas and a worked example from a real round are on how it works.
Verify a draw yourself
We publish the reference verifiers that our own tests run against the server code, so they cannot drift apart:
- verify.py: Python 3, standard library only.
- verify.js: JavaScript for Node or the browser, no dependencies. The results page runs this same file.
curl -O https://pickfaire.com/brand/faire/verify.py
python3 verify.py https://pickfaire.com/d/DRAWCODE/verify.jsonThe script downloads the locked list, checks its hash, fetches the round from a drand relay (not from us: api.drand.sh, api2.drand.sh, api3.drand.sh, drand.cloudflare.com), recomputes the seed and the shuffle, and compares the winners. It ends with "Everything matches." Step by step, with both files in full: verify a draw.
Honest limits
- We check that each round's randomness equals SHA-256 of its signature and that the round number matches. We do not check the BLS signature itself in our code; drand's own client can, against the League of Entropy's public key.
- If the relays do not answer, the draw waits and retries with the same round. It is never drawn with any other randomness.
- The beacon makes the pick fair. It does not make the entry list complete: Instagram hides some comments from everyone, and every page shows comments read next to Instagram's count.
Questions
What is drand?
A public randomness beacon run by the League of Entropy, a group of independent organisations. Its quicknet chain publishes a signed random value every 3 seconds that anyone can fetch and check.
Could the beacon be rigged in favour of one entrant?
The beacon does not know your giveaway exists. The round is fixed before its value is published, and the value comes from a threshold of independent operators, so neither the host, nor us, nor a single operator can choose it.
Why wait for a later round instead of using the current one?
Because the current round is already public. Waiting at least 20 seconds after the lock means the number did not exist when the list was frozen.
Do I need to code to verify a draw?
No. Every results page has a button that re-runs the draw in your browser with the same code as verify.js. The scripts are there for anyone who wants to check independently.
Can the host redraw until a friend wins?
Every redraw uses a new, later beacon round and is labelled on the results page with the earlier winners. Every draw ever locked on the post is on its public ledger, and the host cannot delete those rows.