Verify a bet
Recompute a provably fair result from its seeds or round hash with the casino's own published algorithm, and check the commitment it showed you before play. 6 casinos, 64 games. Everything runs in your browser; nothing is sent anywhere.
The casino commits
Before you bet it shows you a hash: of a secret server seed, of a round in a pre-made chain, or of a signed random value. A hash cannot be reversed, but it pins the secret down.
You bet
Your client seed and nonce, or the round you joined, go into the result together with the secret. The casino cannot change the secret without breaking the hash it already showed.
The secret is revealed
After the bet (or when you rotate your seed pair) the secret is published. Anyone can hash it, compare it with the commitment, and recompute the result from the casino’s own algorithm. That is what this page does.
The casino shows you the hash of a secret server seed before you bet; you add your own client seed and a nonce that counts your bets. Once you rotate the pair, the server seed is revealed and every bet on it can be recomputed.
Every round comes from one long chain of hashes made before launch. The casino publishes the last link in advance; hashing a round backwards reaches it, and a salt chosen after the commitment (a Bitcoin or Ethereum block hash) turns each link into a result.
Each round's random value is the output of a verifiable random function under the casino's public key. The proof shows the value came from that key and the round's request, and the game outcome is derived from the value.
What this does not cover
Only originals the casino documents well enough to reproduce are here: no slots, live games or sports. Where a casino's own sources disagree (Stake's limbo scale, BC.Game's two classic dice verifiers, Rollbit's X-Crash edge), the page says so beside the input it affects. Chain commitments some casinos publish only on social media must be pasted in. The site's own figures are described on the methodology page.