Use the Provably Fair Checker
Provably Fair Checker
Check server seed commitments, generate HMAC-SHA256 hashes, reproduce Dice rolls, estimate Crash points and rebuild Mines layouts where the selected algorithm mode matches the casino implementation.
What the Provably Fair Checker Can Verify
| Mode | What It Checks | Confidence Boundary |
|---|---|---|
| Server Seed Hash | SHA-256 of a revealed server seed against the hash saved before play. | Confirms the commitment only; it does not reproduce the game result. |
| HMAC-SHA256 | Raw HMAC digest for a chosen key, message and encoding. | The casino may use a different key order, separator, cursor or encoding. |
| Dice | Duel-style modulo 10001 plus two generic conversion references. | Select the exact platform conversion before treating a match as evidence. |
| Crash | Generic 52-bit reference formula from HMAC or an existing hash. | Edge factors, instant-bust rules and rounding vary between platforms. |
| Mines | Generic HMAC byte-stream Fisher-Yates layout for a 5×5 board. | A different byte cursor, seed encoding or shuffle method produces another board. |
JSON Import: Recognized Fields
The importer scans standard JSON objects, including nested objects, and recognizes common naming styles such as camelCase, snake_case and lowercase API keys.
| Detected Data | Common Key Examples | How It Is Used |
|---|---|---|
| Revealed server seed | server_seed, serverSeed, serverseed | Filled into commitment, Dice, Crash and Mines fields. |
| Client seed | client_seed, clientSeed, clientseed | Filled into supported game modes. |
| Nonce | nonce, round_nonce, roundIndex | Used as the completed-round counter. |
| Commitment hash | public_hash, server_seed_hash, commitmentHash | Filled as the expected SHA-256 commitment. |
| Secret salt | secret_salt, secretSalt, secretsalt | Loaded only as an HMAC key because its role is provider-specific. |
| Displayed Dice roll | roll, displayed_roll, diceRoll | Used for an optional Dice match comparison. |
| Game hint | game, game_type, mode | Opens Dice, Crash or Mines when the value is clear. |
Auto-detection saves copy-and-paste work; it does not identify an undocumented casino algorithm. Confirm the seed encoding, message format, game conversion and any extra salt or cursor rule before interpreting the result.
How to Verify Server Seed, Client Seed and Nonce
- Save the commitment before play: copy or screenshot the server seed hash.
- Save the completed-round inputs: keep the client seed, nonce, game type and visible result.
- Reveal or rotate the server seed: the hidden seed must be disclosed before full verification.
- Paste JSON or fill the fields: check every auto-detected value before running a mode.
- Verify the commitment first: a matching SHA-256 hash establishes the pre-bet commitment.
- Run the correct game mode: reproduce the displayed result only with a confirmed matching algorithm.
For a detailed explanation of commitments, HMAC construction, nonce handling and platform differences, use the separate How to Verify Provably Fair Games guide.
What a Match Proves
| Finding | Supported Conclusion | Unsupported Conclusion |
|---|---|---|
| Commitment hash matches | The revealed seed matches the hash saved before play. | The payout table is fair or the casino is safe. |
| HMAC digest matches | The same key, message and encoding produced the same digest. | The selected game conversion is correct. |
| Game result matches | The completed outcome is consistent with the tested disclosed algorithm. | The game has 100% RTP or future rounds can be predicted. |
What This Checker Cannot Prove
- RTP or house edge: payout calibration requires a separate multiplier or paytable audit.
- Future outcomes: active server seeds should remain hidden in a proper commitment system.
- Withdrawal safety: cryptographic verification does not test solvency, KYC or account restrictions.
- Licensing quality: a valid round can still occur on a weakly regulated platform.
- Undocumented algorithms: a generic mode cannot validate a proprietary conversion without its specification.
How to Diagnose a Mismatch
- Remove leading or trailing whitespace from all copied fields.
- Confirm that the server seed has already been revealed.
- Check whether the seed is interpreted as UTF-8 text or hexadecimal bytes.
- Verify the nonce and whether counting starts at 0 or 1.
- Confirm separators, field order and any cursor or salt value.
- Select the correct result conversion and rounding rule.
- Preserve the original bet data before contacting support.
Related Audits and Tools
- How to Verify Provably Fair Games — detailed educational workflow.
- Provably Fair Predictor Scams — why seed verification cannot predict hidden future results.
- Duel Dice audit — roll conversion and multiplier pricing are separate checks.
- Duel Crash audit — crash distribution, target math and implementation caveats.
- Duel Mines audit — board generation and multiplier formula.
- Mines RTP audit checker — paytable math rather than hidden-board verification.
- Casino Math Tools — full tool index.
Frequently Asked Questions
Does the JSON importer upload my data?
The provided checker parses JSON and runs Web Crypto calculations in the browser. The shortcode contains no AJAX or fetch request for seed data. Use revealed completed-round inputs only because other scripts or extensions on the device are outside this tool’s control.
Why was my secret salt not used as the server seed?
Different providers assign different roles to a secret salt. The importer loads it only into the raw HMAC key field and warns you to confirm the platform specification.
Can the checker automatically identify the casino?
No. It can read a game hint such as Dice, Crash or Mines, but it cannot infer an undocumented operator algorithm from field names alone.
Can I verify a round before the server seed is revealed?
You can save the commitment hash, but complete verification requires the revealed seed after rotation or completion of the seed cycle.
Does a matching result prove 100% RTP?
No. It supports outcome integrity for one tested round. RTP depends on the payout formula, paytable and any allowance or reward mechanism.
Can this predict the next Dice roll, Crash point or safe Mines tile?
No. A proper provably fair system hides the active server seed. This tool checks completed outcomes after the relevant inputs are disclosed.
Bottom Line
Use this page as an execution tool: paste completed-round JSON, verify the server seed commitment, and reproduce a result only when the selected mode matches the casino’s documented algorithm.
Keep the conclusion narrow. A matching output supports the integrity of the tested round. It does not establish RTP, platform safety or future results.
