How to Verify a Bink Result
Every Bink Original is provably fair. That means you can verify, with cryptographic certainty, that the result of any round you played was determined by a seed Bink committed to beforethe bet — not chosen after. Here's how.
What you need
- Your committed server-seed hash (visible in Settings → Provably Fair before any round).
- Your client seed (visible in the same place; you can change it any time).
- The nonce of the round you want to verify (round number — also visible in your bet history).
- After seed rotation: the revealed server seed.
Step 1 — Confirm the seed wasn't swapped
Take the revealed server seed and hash it with SHA-256. The output should match the committed hash you recorded before any bets were placed. If it matches, the server never changed the seed mid-session.
Step 2 — Re-derive any round outcome
Compute HMAC-SHA256(serverSeed, clientSeed + ":" + nonce). The first 8 bytes of the output map to a 0.00–100.00 float; the rest of the bytes feed game-specific outcome mappers (Dice maps the float to a roll, Plinko maps it to a peg sequence, Roulette maps to a slot, and so on).
If you don't want to run the math by hand, paste the triplet (serverSeed, clientSeed, nonce) into the live verifier at /provably-fair or the per-game verifier at /games/<game>/verify. It returns the exact outcome the server produced.
Step 3 — Read the open source
The outcome-mapper for every Bink Original lives in packages/crypto-utils/src/games/. It's open-source — you can audit the exact code that ran on the server for every round you played.
What this proves
If a single round's computed outcome diverges from what Bink showed you, the server tampered with the seed. There has never been such a divergence — but the point is you don't need to take Bink's word for it. Verify any round, any time.
Try Bink free
Free Gold Coins + free Bink Cash on signup. No purchase necessary. 18+. Available in 39 U.S. states.