Reproduce a disclosed result, compare its hash and inspect the captured payout rules.
Verified
Enter the full hash saved before play. A hash copied afterwards does not establish earlier timing. Why timing matters
Inputs stay in this browser and are not added to the URL. A matching supplied hash does not prove it was recorded before the bet. The payout check covers the announced multiplier, not currency rounding or settlement.
How BCH.games turns seeds into a roll
BCH.games uses HMAC-SHA256 with the server seed as key and client seed, nonce and block counter as the message. It turns the first four bytes into a value below one and scales it to a result from 0.00 to 99.99. Roll Under wins below your target, Roll Over above it; a tie loses. The announced gross payout is 98% divided by nominal win chance, rounded to four decimals.
Check your roll in 4 steps
Rotate your seed pair at BCH.games to reveal the server seed used for the bet.
Paste the revealed server seed, client seed and exact bet nonce. Add a saved pre-bet hash if you have one.
Optionally add the direction, target and announced multiplier.
Press Replay Dice result and compare with your bet history.
Evidence and scope
Game 11,807,862,209 uses nonce 4, Roll Under 96.30, and records result 28.08. The supplied server seed hashes correctly, the result replays, and the announced multiplier matches 1.0177x.
Game 11,807,938,076 uses nonce 14, Roll Over 61.45, and records result 12.11: a loss. Its revealed seed hash and result match, and the announced multiplier is 2.5428x.
Game 11,807,972,487 adds the complete commitment sequence. The active server seed hash was captured at 16:38:33 UTC with zero bets made. The wager followed at 16:39:18 UTC: nonce 3, Roll Over 99.43, result 77.37, a loss, and announced multiplier 175x. The server seed was disclosed at 16:39:58 UTC. Its SHA-256 matches the saved pre-bet hash, and both the result and announced multiplier replay.
This supports Verified for BCH.games Dice v1. The earlier two rounds retain their post-bet hash evidence; their captures alone do not establish pre-bet commitment. BCH.games Plinko has separate evidence and status.
Algorithm
HMAC-SHA256 uses the UTF-8 server seed as key and clientSeed:nonce:0 as message. The first four bytes form a big-endian unsigned integer. Divide by 2³², multiply by 10,000, take the floor and divide by 100. Dice uses one fraction; it does not use a Plinko path.
Rules and payout
The captured client declares a 2% house edge. It uses strict Under/Over comparisons, limits targets to 0.01–97.99 for Under and 2.00–99.98 for Over, and rounds the gross multiplier to four decimal places. Decimal result bins have slightly unequal counts of 32-bit preimages; calculations account for that mapping. Currency settlement rounding is not verified.
Sources: BCH.games published fairness code and Dice client, captured October 25, 2026. Only sanitized disclosed inputs and public rule modules were retained; the raw network capture and account credentials are not part of the repository.
FAQ
What does Verified cover?
The captured Dice v1 algorithm reproduces disclosed results, including a round with a matching server seed hash recorded at zero bets before the wager. It covers that replay evidence and checked payout rules. It does not certify currency settlement, withdrawals, future versions or the operator as a whole.
Are the seeds submitted to a server?
No. The replay uses browser cryptography. Seeds are not submitted by this form, added to query parameters or recorded by analytics.
