What is a ProvablyFair.org Certification?
Provably fair has no industry-wide standard. Casinos define it themselves, typically limited to verifiable randomness — but randomness alone doesn’t prove a game is fair. A provably fair system must be transparent end-to-end: the commitment scheme, the RNG algorithm, the game logic, the payout structure, and the advertised RTP must all be independently verifiable. ProvablyFair.org defines and enforces that standard.
- Provably Fair Bets Recomputed
- 100%
- RTP Claim Band
- 0.1 pp
- Core audit requirements
- 5
- Code, data & findings
- Open-Source
What We Verify
Every audit answers five questions
- 01
Can the casino change your outcome after you bet?
We verify the cryptographic commitment that locks the result before you play.
- 02
Is the randomness real?
We independently implement the algorithm and prove your seed genuinely affects every outcome.
- 03
Does the game follow its own rules?
We recompute every provably fair bet in our dataset. 100% must match. Zero tolerance.
- 04
Is the house edge honest?
We compute the RTP of every setting from first principles, never trusting the casino’s own numbers, and hold it to the figure the casino shows players.
- 05
Does the system hold up under pressure?
We check the game can’t be gamed — seed substitution, stake-dependent outcomes, nonce and multiplier tampering — and, at the deeper level, probe the game’s API directly.
You don’t have to trust us. You can check our work.
We also provide an independent verification tool so you can verify any bet yourself. For every game it supports, it is checked against the same code we used in the audit — and it is not controlled by the casino.
Every finding, every dataset, and every line of verification code is published in an open-source repository.
THE FLOW OF PROOF
From a live bet to independent proof.
How each audit section maps to the casino’s outcome pipeline.
01 / THE LIVE GAME
Outcome generation
Seed inputs
Server + client + nonce
RNG algorithm
Deterministic computation · f(inputs)
Deterministic outcome
Computed from the seeds
Payout applied
Multiplier × bet amount · × stake
Live result recorded
The player sees the outcome
Inputs, results and payouts become audit evidence.
02 / OUR INDEPENDENT CHECKS
Audit & validation
Live bets captured
Real-money data collected
Seed & determinism
Commitments, reveals and nonce · S1
RNG & entropy
Validate the randomness model · S2
Verifier parity
Independently replay the outcome · S3
RTP & payout
Derived game math and the RTP claim · S4
Fairness integrity
Non-standard conditions · S5
Evidence informs the certification verdict.
Five scored checks, plus player verification and a reproducible audit package.
Framework Structure
Audit Overview
ProvablyFair.org evaluates the fairness of provably fair casino games through a structured, evidence-based audit framework. Every audit follows the same methodology regardless of game type, casino, or seed architecture.
Claim
What the casino says
Evidence
What the audit establishes
Independent verification
What anyone can reproduce
Claims require proof. Proof requires evidence that anyone can independently verify.
The framework consists of five scored audit sections (S1–S5) and two transparency sections (S6–S7). Sections 1–3 are cryptographic foundations — a single failure means the game cannot be provably fair by definition. Sections 4–5 test the game logic and implementation integrity. Sections 6–7 ensure the audit itself is player-accessible and fully reproducible — they are not scored but are required for certification.
Cryptographic foundations
A failure means the game cannot be provably fair.
Game & implementation
Test the payout math and fairness integrity.
Public transparency
Required for certification, not scored.
Game profiles
The seven sections are the same for every game. What each game must pass is set out in its game profile: a numbered list of checks, 30 to 39 per game type, mapped onto S1–S7. A Plinko audit at one casino and a Plinko audit at another answer the same numbered checks, and every audit publishes which of its tests covers which check. Profiles are versioned, and every audit names the profile version it was checked against.
A typical per-game audit involves thousands of real-money bets placed and individually verified, tens of millions of simulated rounds for statistical validation, and a purpose-built verification codebase written independently from the casino’s own code.
Every audit produces a public, open-source repository. Anyone can clone it, run the test suite, and independently verify every finding. The repo is the credential.