Duel.com Guide: how-to-verify-provably-fair (Step-by-Step)
Tested step-by-step. Screenshots, exact button labels, and the gotchas to avoid.
Why bother verifying a provably fair round?
Provably fair is one of the genuine arguments for playing on a crypto casino instead of a regulated EU site. Regulated sites publish RTPs but you trust the operator and a third-party tester (e.g., eCOGRA, iTech Labs) to enforce them. Provably fair flips the trust: every round result is determined by a public formula combining a server seed (committed before the round), your client seed, and a nonce (round counter). You can independently recompute the result and confirm Duel did not pick the outcome after seeing your bet. The catch: most players never actually verify. They take "provably fair" on faith. This guide walks you through a real verification in under a minute, explains the seed mechanics, and shows you exactly which tool to use. Reference: provablyfair.com.
What will you verify?
For each round of a Duel Original (Crash, Dice, Plinko, Mines, Duel Blackjack, Beef), you will independently confirm that the result was determined by the seeds before the round started, not retroactively chosen by Duel. The verification proves two things: the server seed Duel revealed matches the hash they committed before the round, and the published seed/client-seed/nonce triple deterministically reproduces the result you saw.
How do seeds work? Client + server + nonce explained.
The mechanism is three inputs combined deterministically. The server seed is a random string Duel generates and hashes with SHA-256 before any round starts; the hash is published to you but the seed itself is hidden. The client seed is a string you set (or accept a random default) and can change anytime, which prevents Duel from precomputing results because they don't know your seed in advance. The nonce is a round counter that increments each bet (1, 2, 3, ...) so even with the same seeds, each round derives a unique result. To produce the result for a round, Duel hashes the combined string (typically HMAC-SHA256 with the server seed as key and `client-seed:nonce` as message), then converts the hash bytes to a number in the relevant range (a multiplier for Crash, a position for Plinko, etc.). The math is public.
Step 1: Open Account, then Provably Fair
Find the Provably Fair section in your account menu (sometimes labelled "Fairness"). The page shows your current client seed, current server seed hash, and round counter. On mobile, this lives under the avatar menu, scroll to Provably Fair.
Step 2: Note your current client seed and server seed hash
Client seed: a string you set, or random default Duel assigned. Server seed hash: SHA-256 of Duel's current server seed (the seed itself is hidden until reveal). Copy both to a notepad. The hash will be your check value: when Duel reveals the seed later, you hash the revealed seed and compare it to this stored hash; they must match.
Step 3: Play some rounds
Play any Original (Crash, Dice, Plinko, Mines, Duel Blackjack, Beef). Note the nonce (round counter) and result of one round you want to verify, plus the client seed and server seed hash from Step 2. The nonce is visible on the round result; some games show it inline, others under "details".
Step 4: Rotate server seed
In Provably Fair settings, click "Rotate server seed". Duel reveals the previous server seed and switches to a new one (with a fresh hash for the new seed). You can now verify all rounds that used the previous seed. The reveal step is critical: until you rotate, the server seed is hidden and cannot be checked.
Step 5: Verify the hash matches
Hash the revealed server seed with SHA-256. Compare to the previously published hash. If they match exactly (every character), the seed was genuinely committed in advance. Duel could not have manipulated the seed after seeing your bets. Any hash tool works: a command line `sha256sum`, an online SHA-256 calculator, or our verifier which does this in one click.
Step 6: Re-derive the round result
Use our provably fair verifier or Duel's built-in verifier. Input the server seed, client seed, and nonce. The tool reproduces the round result deterministically. If it matches what you saw in-game, the round was honest. If it does not match, you have evidence of tampering: file with support immediately, save your seed records, contact us.
Verify a Crash round from yesterday in 30 seconds
Concrete walk-through. Open your bet history, pick a Crash round (e.g., 2.34x cash-out at nonce 1247, client seed `kj7s9a2`, server seed hash `9f8a...c2d1`). Rotate the server seed on Provably Fair, which reveals seed `b7e3d9f1...4a82`. Hash the revealed seed with SHA-256 using any tool: result should equal `9f8a...c2d1`. If yes, commit verified. Now open the verifier, paste server seed `b7e3d9f1...4a82`, client seed `kj7s9a2`, nonce 1247, game type Crash. The verifier outputs the crash multiplier: 2.34x. Matches your bet history. Round verified. Total time, less than 60 seconds once you know the flow.
Pro tips from real testing
- Rotate seeds monthly: Long-lived seed pairs reduce overhead but limit how far back you can verify. Monthly rotation balances effort against audit depth.
- Use a third-party verifier occasionally: Duel's built-in verifier is convenient but technically you are trusting Duel to compute the right answer. A third-party verifier (or self-coded script) closes the loop.
- Browser-side vs third-party comparison: Run the verification in-browser on Duel's tool for speed, then once a month re-verify a sample on an external SHA-256 calculator. They must agree.
- Save a record of seeds before rotating: Once rotated, the previous seed is no longer "current"; if you forgot to copy it, the history view still preserves it. Better practice is to log it before rotating.
- Verify after big wins: Not because you suspect cheating; doing it proves to yourself the result was deterministic. Useful for accounting and tax records too.
Common verification issues and troubleshooting
- Hash does not match the revealed seed: Either a copy-paste error (whitespace, missing character) or evidence of tampering. Recompute the SHA-256 carefully; if it still does not match, file a support ticket with your records.
- Verifier output does not match game result: Confirm you used the right nonce. Off-by-one is the most common mistake (round 1 has nonce 1, not 0, on most Duel games).
- Cannot find the nonce for an old round: Bet history shows nonce next to each round. If history is paginated past 30 days, export the CSV.
- Server seed hash does not appear in settings: Account is new or seeds were just rotated. Play one round to initialize, then refresh.
- Multiple games with same nonce showing different results: Expected. Game type is an input to the derivation; same seed/nonce, different game, different result.
- Third-party verifier disagrees with Duel's verifier: Double-check you selected the right game type and that the verifier handles HMAC-SHA256 (not plain SHA-256) for Duel's specific scheme. docs.duel.win publishes the exact formula.
What happens next?
Round verified, you can move on or audit a sample of further rounds for confidence. For ongoing fairness checks across all Originals, our provably fair verifier handles all six game types. For background on provable fairness as a concept and how Duel's implementation compares to other crypto casinos, see our provably fair explainer. To dig into the game-specific math (e.g., Crash curve distribution, Plinko payout matrices), our Originals overview covers each title with verified RTP.