Dice verifiers

Choose the operator used for your bet. Verified and Reference describe replay evidence for a specific adapter.

Sorted alphabetically.

BC.GameVerifiedDice · algorithm v1Dice98 and ClassicDice98 replay captured outcomes. Pre-bet settings screenshots record matching hash prefixes; clipped values and screenshot-time provenance are documented on the verifier.Open verifier
BCH.gamesVerifiedDice · algorithm v1Disclosed Dice results and announced multipliers replay, including a complete pre-bet hash and later seed disclosure. Currency settlement is outside this check.Open verifier
Duel.comVerifiedDice · algorithm v1Thirteen captured results match a full pre-bet byte-seed commitment and later disclosure. Verified covers result replay, not general payout tiers or settlement.Open verifier
DuelbitsReferenceDice · algorithm v1Published SHA-256 roll algorithm. Thirteen observed demo rounds have no revealed seed; Reference, not Verified. Payout settlement is outside scope.Open verifier
StakeReferenceDice · algorithm v1Documented HMAC generator and captured fairness mapping. Synthetic examples only; no disclosed Stake Dice round. Reference status.Open verifier

Dice algorithms by operator

Supported Dice replay schemes
Operator	Status	Result range	Published method
BC.Game	Verified, scoped evidence	Dice98: 0.00–99.99; ClassicDice98: 0.00–100.00	Variant-specific HMAC mapping; choose the matching version.
BCH.games	Verified	0.00–99.99	HMAC-SHA256; seed text key; clientSeed:nonce:0.
Duel.com	Verified	0.00–100.00	HMAC-SHA256; decoded seed bytes; clientSeed:nonce; rejection sampling.
Duelbits	Reference	0.00–99.99	SHA-256 of serverSeed:clientSeed:nonce; modulo 10,000.
Stake	Reference	0.00–100.00	HMAC-SHA256 byte generator with operator-specific rounding.

A 0.00–100.00 display has 10,001 possible values, while 0.00–99.99 has 10,000. Display values are not necessarily equally likely after mapping or rounding. Match the range, comparison and payout rule rather than assuming that every “Over 50” bet has identical odds.

How to check a Dice roll

Rotate your seed pair at the operator to reveal the server seed used for the old bets.
Copy the revealed server seed, client seed and the exact nonce of the bet.
Open the matching operator verifier. For BC.Game, also select the correct Dice variant.
Compare the replayed result with your bet history. If you saved the server-seed hash before betting, paste it too so the verifier can check the commitment.

The replay runs in your browser. Seeds and nonce are not submitted by the form or included in analytics.

FAQ

What do Verified and Reference mean?

Verified adapters reproduce real disclosed rounds with recorded commitment evidence. The evidence can include a clipped screenshot prefix rather than a complete pre-bet hash; see each operator’s scope. Reference adapters implement a documented method but have not yet been matched to a real disclosed round. Neither label certifies an operator as a whole.

Why can’t I use the hashed server seed?

The hash is a fingerprint, not the secret seed used by the HMAC generator. Rotate the seed pair to reveal the old server seed, then use it to replay that round.