How Provably Fair Works
1) Server Seed (Commitment)
The casino generates a secret server seed and publishes its SHA-256 hash before play. This locks the outcome so it cannot be changed later.
2) Client Seed (Your Input)
You provide a client seed (often editable) to influence the randomness. It is combined with the server seed and nonce to create each result.
3) Nonce (Round Counter)
The nonce increments every bet and ensures every roll uses a unique hash even when seeds stay the same.
Verifier (HMAC-SHA256)
Scheme implemented: HMAC-SHA256(serverSeed, clientSeed:nonce). Some casinos add extra fields or use a different delimiter. If your casino differs, compare their documentation and adjust inputs accordingly.
Tip: If the casino uses a different scheme (for example: HMAC-SHA256(serverSeed, clientSeed:nonce:betId) or SHA-512), copy their formula into your own tooling or contact support for their verifier specification.
FAQ
Why do I need both the server seed and its hash?
The hash proves the casino committed to a seed before the game started. When the seed is revealed, you can recompute the hash to confirm it matches the commitment.
What if my computed hash does not match?
First verify the exact client seed, nonce, and delimiter. If everything matches and the hash still differs, contact the casino and provide the bet ID for investigation.
Does a matching hash mean the game is fair?
It proves the result was derived from the committed seeds. Fairness still depends on the casino using a transparent formula and honest bet-history data.
Why do some casinos show a different formula?
There is no single standard. Some games use SHA-512, different separators, or include game IDs and timestamps. Always follow the casino's published formula.