Check the bet, not the promise.
Every finished JuiceBet result can be reviewed through bet ID, server seed, server seed hash, client seed, and nonce.
bet_91b804115732435780cf52...1a7d2f851276697235...406fca562d53Seed revealed
Use $verify bet_id to compare derived result and stored result.
The data that matters.
This page explains what players see and what staff monitors. It does not claim magic. It makes the result reviewable.
Server seed hash
Shown before a game resolves. It commits the bot to a hidden server seed before the final outcome is known to the player.
Server seed
Revealed after the result. The reveal lets the player verify that the earlier hash matches the finished bet.
Client seed
A player related input used with the server seed. It keeps the calculation tied to the bet session.
Nonce and bet ID
The nonce prevents reused output. The bet ID links the final result, payout, seed reveal, and stored ledger entry.
Run the audit command.
After a bet closes, run $verify bet_id. JuiceBet shows the seed data, derived result, stored result, and game specific details.
Tracked by staff.
Admin analytics track wager, payout, profit, RTP, expected RTP, deviation, biggest wins, and suspicious windows. Public pages explain the concept without leaking edge settings.
Designed around real bot abuse cases.
Replay clicks, duplicate sessions, old buttons, duplicate seeds, duplicate nonces, and private data leaks are treated as audit surfaces.
Duplicate seed and nonce checks
The admin fairness page tracks duplicate bet IDs, duplicate seed hashes, duplicate server seeds, and duplicate nonce pairs.
Anti replay
A closed session should not pay twice because someone clicked an old button or replayed an interaction.
Privacy mode
Private players appear as Private Player on public boards, results, races, and activity cards.
Auditable and monitored.
JuiceBet is built to be checked, logged, and reviewed. If a fairness mismatch appears, staff can inspect the bet, seed health, duplicate warnings, RTP deviation, and related logs.