Every bet you place is cryptographically committed before you see the result. After you rotate your server seed, you can verify any past bet using only public values and the revealed secret.
Paste a bet ID to open the bet detail and inspect fairness data.
Find bet IDs on My Bets. Fairness values come from the API; we do not recompute HMAC in the browser.
Step 1
Before any bet, the server publishes a hash of a secret server seed. That hash is your commitment and stays visible to you. You also set a client seed (we generate one from your wallet by default, and you can change it in Settings → Fairness).
Step 2
For each bet, the server uses the secret server seed, your public client seed, and a per-seed nonce that goes up on every bet. It feeds them into HMAC-SHA256; the 64-hex output seeds the game engine. Those inputs are fixed by the commitment — the operator cannot change them after the fact.
Step 3
When you rotate your server seed, the previous secret is published. You can then verify every bet that was made under that commitment. The exact message format is part of the bet record. Anyone can recompute HMAC in OpenSSL, Python, or a browser and confirm the output matches.
Values are illustrative. Your real bet shows the exact message, seeds, and output from the verify endpoint.
serverSeed: a3f2c8…e9b1 (64 hex) clientSeed: my-lucky-seed nonce: 47 message: cluster-slot:my-lucky-seed:47 algorithm: HMAC-SHA256 HMAC-SHA256(serverSeed as key, message as UTF-8) = 7d4e8f1c…a2b3 └ 64 hex → fed into the game engine PRNG
Settings → Fairness for your active commitment, client seed, rotation, and history.