Reproduce this audit
Re-run our findings on your own machine, with the same code and data we used.
Fully open source. Publicly checkable.
Provably fair games let any player check a bet against the math. We built our audit framework on the same principle: an audit of a “verify-it-yourself” product should itself be something anyone can verify.
Run the audit locally
Each game has its own repository: verifier code, real bets recorded from the live game, and a simulation harness. Clone a repository, install its dependencies, then run the full suite.
git clone https://github.com/ProvablyFair-org/duel-plinko.gitcd duel-plinko && npm installnpm testUnit tests → simulation → verification steps
What npm test runs
Each game is checked in the same core areas, with extra checks for its own mechanics.
01Seed & commitment integrity
The game locks in a hashed server seed before you bet — so it can’t change the outcome after seeing your wager. Every seed is checked against its hash, and the chain of seeds is followed bet to bet.
Seed Hash Integrity · Commitment Linkage · Hash Consistency · Nonce Audit02Outcome recomputation
Every recorded bet is replayed from its seeds using the game’s published algorithm. The rebuilt outcome has to match the live result exactly, including how the player’s client seed affects it.
Outcome Recomputation · Client Seed Influence03Payout & math
Payouts and the house edge are recalculated from first principles, every multiplier matched to the game’s published rules, confirming the game pays exactly what its own rules say — at every bet size.
Payout Math · Multiplier Provenance · House Edge Audit · Bet-Size Invariance04Dataset & odds integrity
The bet data is hash-verified so it can’t have been altered, and the game’s odds are derived independently — not taken on trust — guarding against a result that’s only “fair” by its own circular math.
Dataset Hash · Anti-Circularity · Config Completeness · Epoch Size · Phase Labels05Monte Carlo simulation
Millions of simulated rounds test whether outcomes hold up as fair over the long run — and a second pass checks that no specific seed or window was cherry-picked to look clean.
Simulation Pass 1 — Integrity · Simulation Pass 2 — Cherry-Pick06Game-specific checks
On top of the core, each game adds checks for its own mechanics — card rules, cascading wins, multi-step reveals, drand timing, and more. Each game’s full suite runs 15–33 checks depending on how complex it is.
Varies per gameWant to check your own bets?
The suite runs against the dataset included in each repo. Swap in your own dataset in the same format and re-run — npm test verifies whatever data it’s given. Every repository includes the capture script used to record the original bets, so you can collect your own.
Watch a walkthrough
The whole process end to end — clone, install, run, and read the output.
Clone. Install. Run. Read.
$ git clone https://github.com/ProvablyFair-org/duel-plinko.git
$ cd duel-plinko && npm install
$ npm testAll 10 game repositories
Each repository contains the verifier code, datasets and test suite. Full step-by-step results and findings live on each game’s audit page.
