WOYALE. Verify a bet
Fair play

Provably fair, explained

A provably fair game publishes a fingerprint of its result before you bet, then shows you the key afterwards. These guides show what that proves, what it doesn't, and how to check it yourself.

A receiver reaches for the ball under stadium lights
5

Guides in this section

21

Minutes to read them all

Check a roll yourself

The verifier runs in your browser.

How provably fair works

A provably fair game locks in its result before you bet and lets you check it afterwards. The site picks a secret value, the server seed, and shows you only its SHA-256 hash. A hash works like a fingerprint: it identifies the seed exactly, but you can’t work the seed out from it. You add your own value, the client seed, and every bet you place raises a counter called the nonce.

When you rotate seeds, the site reveals the old server seed. You can then hash it yourself and check that it matches the fingerprint you saw before betting. If it matches, the site could not have swapped the seed once your bets were in. Run the seeds and nonce through the game’s published formula and you get the same result the site gave you.

That’s the commit-reveal idea in full. What is provably fair explains it slowly, and server seed, client seed and nonce covers each value and when it changes.

What you can check, and what you can’t

A matching result proves one narrow thing: the outcome was fixed before you bet and follows the formula the site publishes. It’s a real guarantee, and it’s easy to read more into it than it gives you.

You can checkYou can’t check with seeds
The server seed wasn’t changed after you betWhether the site pays out what you win
The result follows the stated formulaWhether the house edge is what’s advertised
Your client seed was usedWhether the site is licensed or solvent
Each nonce gave the reported resultSports bets, odds or how games are settled

The last row matters most on a betting site. Provably fair covers casino-style originals such as dice, crash, limbo, plinko and mines. A bet on a football game is settled by a real match, and no seed decides it. What provably fair doesn’t prove covers the gaps one at a time.

Check one roll in five minutes

You need four values from the site’s fairness page: the revealed server seed, the hash you saw before betting, your client seed and the nonce of the bet. Paste them into the dice verifier. It hashes the seed, compares the hash, and recomputes the roll in your browser.

For the method by hand, with every intermediate number, read how to verify a provably fair dice bet. Other games use the same HMAC output in different ways: how one HMAC result becomes a dice roll, a multiplier or a shuffled deck walks through the common patterns, and why the site’s own formula always wins when it differs.

Habits that make checking possible

  • Write down the hashed server seed before you play. The check means nothing if you only see the hash after the seed is revealed.
  • Set your own client seed. A default you didn’t choose gives you less assurance that the site couldn’t plan around it.
  • Rotate seeds when you finish a session. Bets made on the current seed can’t be checked until it’s revealed.
  • Keep the nonce of any bet you want to dispute. Without it you can’t find the bet again.

Read in this order

Start with what provably fair is, then the seeds, then a worked check. Read the limits page before you rely on a fairness badge for anything more than a single result.