Trust
Provably fair
Every result is fixed by a commitment published before you bet, so neither you nor the casino can change it afterwards — and you can recompute it yourself.
Verify a round
Runs entirely in your browser with the same code the server uses.
Enter the round's 64-character game hash.
Sign in to manage your seeds and verify your own bets.
Sign inThe three ingredients
- Server seed — 32 random bytes generated by mulletbet. Before any bet you see only its
SHA-256hash: a fingerprint that commits us to the seed without revealing it. - Client seed — a value you choose, so the casino cannot pick a seed that targets you. You set it when you rotate, after the next server seed's hash is already published.
- Nonce — a counter that increases by one with every bet on the same seed pair. The database guarantees a nonce is never used twice.
How a result is generated
Each round computes HMAC_SHA256(serverSeed, clientSeed:nonce:cursor). Every 4 bytes become a number between 0 and 1, and each game maps those numbers to its outcome — the exact formula for each game is in the verifier's source and in docs/PROVABLY_FAIR.md. For Dice: roll = floor(float × 10000) / 100, a number from 0.00 to 99.99.
How you verify it
- Note the hashed server seed shown before you play.
- Play as many rounds as you like.
- Rotate your seed pair. The previous server seed is revealed — check that its
SHA-256matches the hash you saw before playing (the verifier does this for you). - Recompute any round from the server seed, your client seed and its nonce.
Crash
Crash is multiplayer, so a single round can't use your personal seeds. Its results come from a pre-generated chain of hashes whose final value is published in advance; each revealed round hash can be checked against the next.