Provably fair verification checks whether a recorded result is consistent with committed inputs and a published algorithm. It does not certify a casino’s solvency, licence, withdrawal practices or overall honesty. A verification badge without reproducible inputs is not the same as a completed check.
What to record before and after a round
In a common commit-and-reveal design, the operator publishes a hash of a secret server seed before play. The client seed and nonce identify the inputs for a particular result. After the server seed is revealed, usually following rotation, its hash can be compared with the original commitment and the result recomputed.
The algorithm matters
Stake’s published implementation provides a concrete example using HMAC-SHA256 with server seed, client seed, nonce and cursor. Other systems may encode inputs or map bytes to outcomes differently. Matching a hash alone does not establish that the correct game-specific outcome conversion was applied.
A practical verification worksheet
- Save the round ID, pre-round commitment and algorithm version.
- Record the exact client seed and nonce, including punctuation and case.
- Obtain the revealed server seed through the operator’s documented process.
- Recompute the commitment and then the complete game result.
- Compare the reproduced result with the immutable round record.
For example, nonce 41 and nonce 42 refer to different inputs. A correct result for nonce 42 does not validate the previous round. Similarly, converting a hexadecimal string into text bytes instead of hexadecimal bytes can produce a different calculation.
What a successful check leaves open
It does not show that a game has favourable odds, that every round was displayed, or that a bot will honour a withdrawal. House edge can be built into an entirely reproducible algorithm. Treat seed verification and operator due diligence as separate questions.
Never paste a wallet recovery phrase, private key or Telegram login code into a verifier. Those secrets are unrelated to game-seed verification. Use documented public inputs and inspect the verification implementation before trusting its output.
Sources
Sources checked on 13 October 2026.