Provably fair games let any player check a bet against the math. We built our audit framework on the same principle — it's fully open source and publicly checkable. An audit of a "verify-it-yourself" product should itself be something anyone can verify.
So every result in the Duel.com audit can be re-run on your own machine. Clone the public repo, run the test suite, and regenerate our findings from the same code and data we used.
The Test Suite
What npm test runs
Each game has its own repository. Inside it: the verifier code, the real bets recorded from the live game, and the simulation harness. One command runs the full pipeline — the unit tests, the simulation, and the verification steps:
$ git clone https://github.com/ProvablyFair-org/duel-<game> $ cd duel-<game> && npm install && npm test
Each game is checked the same core way, plus extra checks for how that game works:
The audit suite
Seed & 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.
Every recorded bet is replayed from its seeds using the game's published algorithm — the result is re-derived from scratch and matched against what the live game actually produced.
Outcome RecomputationClient Seed Influence
Payout & 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.
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.
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.
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.
Want to check your own bets? The suite runs against the dataset included in each repo. To test your own instead, swap in a dataset of your own in the same format and re-run — npm test verifies whatever data it's given. Every repo includes the capture script used to record the original bets, so you can collect your own.
Walkthrough
Watch a walkthrough
The whole process end to end — clone, install, run, and read the output.
Open Source
All 10 game repositories
Each game has its own public repository — verifier code, datasets, and the test suite. The full step-by-step results and findings for each game live on its audit page.