A different verifier output can indicate a real issue, but common causes are an off-by-one nonce, a current seed used for an old round, a copied character error or the wrong game formula. Preserve the original record before repeating the calculation.
Open the live accountSave round ID, result, game/provider version, timestamp, commitment, revealed seed, client seed and nonce. Do not rotate or edit values while comparing tools. Label every value by source so the current fairness panel is not confused with archived history.
Hash the revealed server seed using the documented method. If it does not match the saved pre-round commitment, stop there and report that specific comparison. If it matches, continue to the game-result transformation.
Test the recorded nonce, not a guessed neighbour, and confirm the exact game mode, risk setting or cursor where documented. A verifier for dice cannot validate a crash point merely because both use HMAC.
Provide support one round ID and the non-sensitive inputs, plus the documented verifier and expected versus displayed output. Never send password, two-factor code, wallet private key or seed phrase. Ask which algorithm version generated the round.
No. Use the nonce stored with the round; random matching does not validate the event.
Retired verification inputs are non-credential data, but never share account or wallet secrets.
Confirm the revealed server seed hashes to the saved pre-round commitment.
Last reviewed: 30 July 2026