A provably-fair check begins before play. The game exposes a hash of a hidden server seed, committing to that secret without revealing it. After rotation, the revealed seed can be hashed again and compared with the earlier commitment. Without the pre-round value, a later seed has nothing reliable to match.
Open the live accountOpen the information or fairness control inside the exact game. Record the game name, provider, active server-seed hash, client seed and current nonce before the round. A hash copied from another title, account session or provider cannot validate this result.
Copy the hash as plain text or capture a timestamped screen with the round context. This value is not a wallet key and cannot spend funds. Never include a password, two-factor code, seed phrase or crypto private key; those secrets are unrelated to game verification.
After play, save the round or bet ID and the displayed result. The verifier must use the same seed set and nonce that generated that round. A crash multiplier, dice roll and mines layout can transform the same hash bytes differently, so the game algorithm also matters.
When the server seed is rotated and revealed, hash it with the documented method and compare the complete output character for character with the saved commitment. A matching hash proves the revealed seed matches the earlier commitment; it does not promise a winning distribution.
No. It commits to a hidden seed without disclosing the seed itself.
You need the earlier commitment or a trustworthy round record containing it.
No. It verifies input commitment, not short-term returns.
Last reviewed: 30 July 2026