Fair Play, Verified
Every game round is decided by cryptography you can check yourself.
We commit first
Before a round starts we publish a hash of a secret number (the server seed). It proves we can’t change it later.
You control a seed
You have a client seed and a counter (nonce). They make your rounds unique and verifiable.
Anyone can verify
After the round we reveal the server seed. Combine it with your client seed to reproduce the outcome.
What “Provably Fair” means
It’s a simple promise backed by math: the casino cannot secretly influence a result after you bet. We lock our choice with a public hash, you add your choice (client seed), and the result is derived from both using a standard cryptographic function.
How results are decided
- Commit. We publish
SHA-256(serverSeed)before the round. - Your input. You have
clientSeedandnonce(0,1,2… per bet). - Derive. We compute
HMAC-SHA256(serverSeed, clientSeed:nonce). - Map. The hash is turned into a number and mapped to the game (e.g., 0–36 for roulette).
- Reveal. After the round we show
serverSeed. Anyone can recompute and check.
What this looks like in our games
Roulette
We turn the cryptographic number into an index from 0 to 36. That index is the winning pocket.
- Range used:
37(European roulette). - Same method for Red/Black, Odd/Even – they’re groups of those pockets.
Your controls
Client seed
A string you can change anytime. It’s your personal input into the result.
Nonce
A counter that increases per bet (0,1,2…). It ensures each round uses a different input.
Changing your client seed affects only future rounds, not completed ones.
Manual verifier (advanced)
Formula: index = (HMAC-SHA256(serverSeed, clientSeed:nonce).first8bytes) % range
