Provably-fair infrastructure

Every draw. Verified fair.
In public.

Every prize competition on the ABOS network is cryptographically sealed before it opens and re-derived from public randomness after it closes. The moment an operator tries to manipulate a draw, this board turns red — for the whole world to see.

Network status: all draws fair Verify a draw yourself
2026Register opens
4Checks per competition
0Trust required
100%Independently recomputable
Live register

Four ticks on every comp.

Each competition is sealed on four points — its setup, its instant-win allocation, its entry list and its draw. All four green means nothing was touched after lock-in. Edit a comp, reshuffle the instant wins, or announce the wrong winner and the tick goes red — public, permanent and automatic.

Contacting member sites — every proof below is recomputed live…

Note: the register cryptographically proves draw integrity — that the winner is fair and unriggable. Prize fulfilment (that the operator actually pays out) is tracked separately via verified-winner confirmations and a public dispute log per site.

The mechanism

Four steps. No trust required.

This isn't a promise or a certificate. It's maths anyone can recompute — and because ABOS hosts every member site, reporting to this register is automatic and mandatory, not voluntary.

Same proof, two depths — pick yours
The glass safe

Before a single ticket goes on sale, the draw's secret is locked in a glass safe and the safe's fingerprint is published for anyone to screenshot. From that second, nothing inside can change without the fingerprint breaking — in public.

A coin-toss from the future

The winner isn't picked by us, the site owner, or a button somebody presses. It comes from a public coin-toss service used worldwide — and the toss the draw uses doesn't exist yet while tickets are selling. Nobody can peek at a number that hasn't been created.

Check it yourself

After the draw, the safe is opened in public. Your own phone can re-run the entire draw and land on the same winner. If even one ticket had been moved, the numbers wouldn't line up — and everyone would see it.

Why it matters

The draw date can't quietly move. The prize map can't be shuffled. A mate can't be picked. The operator couldn't fix the draw even if they wanted to — and that sentence is worth more than any "trust us" badge in the industry.

No account, no maths degree, no trust required — the proof page is public on every single draw.
Open a proof

Recompute any draw in your browser.

verify — draw #2214 · Competition Sample Site 3
commitment = sha256(serverSeed)
7f2a…c19e sealed 2026-07-06 09:14 UTC
beacon = drand round 4,192,880
randomness = a1b9…40e2 (fetched independently)
entries = 249 tickets · hash d4c8…9f1
winner = HMAC(seed, entries | round)
→ ticket #188 · Jordan P. (Manchester)
VERIFIED — reveal matches commitment · winner reconciles

The four ticks, checked automatically

Setup — prizes, ticket cap and rules are unchanged since the sealed commitment. No editing a comp after it locks.
Instant wins — the winning-ticket map was fixed before sale and still matches the reveal. Allocation can't be reshuffled.
Entries — the sold-ticket list wasn't altered after close; its hash matches the sealed set.
Draw — the winner is exactly the one derived from the public drand beacon. No cherry-picking.

Any single mismatch flips the site to Failed verification and writes it to the permanent log. There is no path to a quiet fix.

append-only log · hash-chained · anchored publicly daily
#3410 site3·2214 VERIFIED prev=a0f2… → self=bc71…
#3411 site2·4821 VERIFIED prev=bc71… → self=e93a…
#3412 site6·881 FAILED   prev=e93a… → self=4d17… ← immutable