The verification inputs
- Server seed hash
- Commitment published before the hidden seed is revealed.
- Client seed
- Player-visible input combined with the server seed.
- Nonce
- Counter that changes for successive bets under a seed pair.
- Cursor
- Additional position used when a game needs more generated values.
Verification workflow
- Record the server-seed hash, client seed, nonce and game result.
- Rotate the seed pair so the previous server seed is revealed.
- Hash the revealed server seed and compare it with the earlier commitment.
- Use the published HMAC-SHA256 implementation or official calculator to recompute the game output.
- Compare the recomputed value with the recorded result.
What the proof covers
A matching computation supports that the committed inputs produced the displayed result for the supported game. It does not prove local legality, guarantee withdrawal, remove house edge or verify an unrelated third-party provider.
Fair does not mean favorable
A correctly generated losing result is still a loss. Verification changes auditability, not expected value.