How to read the Duelbits game data
Duelbits publishes a provably fair algorithm for its originals. Both implementations here are Reference: they follow published code, but we have not yet matched captured rounds to a later revealed seed. Reference describes our evidence, not an accusation.
What we checked at Duelbits
The published algorithm hashes the text serverSeed:clientSeed:nonce with SHA-256. The first eight hex digits become a 32-bit integer. Dice uses modulo 10,000 and divides by 100; Plinko uses modulo 65,535 to produce a ticket. Its current v2 path and payout mapping are not confirmed.
Thirteen zero-stake Dice observations cover Under, Over and interval modes. Announced multipliers at 20%, 40%, 50% and 80% match 100 / (win chance in percent × 1.01). This implies about 99.01% nominal return before rakeback, but does not verify results or final settlement.
What is still missing
Moving an adapter to Verified requires captured rounds, saved pre-bet commitment evidence and a later revealed server seed that reproduces the results. Seed history did not load during our check, leaving that evidence incomplete. This does not establish manipulation. Plinko also needs its current ticket-to-path and payout mapping confirmed; no Duelbits payout profile is offered in the calculator or simulator.
Before you play
Read the recorded availability rules and current operator terms for your location. A provably fair casino can still have a house edge, account restrictions and withdrawal conditions. Our replay work does not assess payment reliability or licensing.
Use the Dice verifier for a reference roll or the Plinko verifier for a ticket. The methodology explains these evidence limits.
