Liqd.com
Official website ·liqd.com (opens in a new tab)
Independent evidence from Liqd.com’s prelaunch game audit.
Liqd.com
Official website ·liqd.com (opens in a new tab)
Independent evidence from Liqd.com’s prelaunch game audit.
PF-2026-LIQD · Framework v1.1
Audit published 23 Oct 2026
23 Oct 2026
Not yet certified. Final certification requires public launch and an independent recheck of live bets using anonymous, self-funded accounts.
Published audit record
View full record → (opens in a new tab)Published audit record
- Prelaunch audit
Framework v1.1 · Pre-launch tests passed
39,400 bets - Fixes re-verified
Every disclosed finding resolved
10 findings fixed - Public-site recheckNov 2026
After public launch · Pending
If a result feels wrong
PF-2026-LIQD · Framework v1.1. The evidence comes from the pre-launch environment. Public player checks are coming after launch. Full findings and supporting evidence remain in the technical report.
01Per-game resultsGame results
6 games passed the pre-launch audit. Inspect each game’s RTP, report and source code.
| Game | Captured bets | RTP · Proven | RTP · Simulated | Result | Evidence |
|---|---|---|---|---|---|
| Blackjack | 6,000 | 99.512325% | 99.5230%30M rounds | ||
| Mines | 6,900 | 99.0000% | 98.9427%24M rounds | ||
| Plinko | 10,100 | 99.0152% | 98.9249%28M rounds | ||
| Dice | 6,700 | 99.0000% | 99.0203%98M rounds | ||
| Limbo | 6,700 | 99.00% | 99.0128%38M rounds | ||
| Keno | 3,000 | 98.9867% | 99.0143%Standard modes · 10M total rounds |
- Bets captured
- 6,000
- RNG type
- HMAC-SHA256
39,400 prelaunch audit bets in the published record. RTP uses each report’s tested configuration and strategy; Plinko and Keno show the mean across settings.
02What this audit covers
Game fairness, clear boundaries and ongoing evidence.
Audited
6 original games in the published scope
Seed commitments, nonce & randomness
Prelaunch bets independently replayed
Payout calculations & game RTP
Adversarial fairness & input checks
Prelaunch capture · July–October 2026
Ongoing verification
Certification requires public launch and a fresh capture of bets through anonymous, self-funded accounts.
The launched build must match the audited implementation. Changes to game rules or payout tables require re-audit.
Audited
6 original games in the published scope
Seed commitments, nonce & randomness
Prelaunch bets independently replayed
Payout calculations & game RTP
Adversarial fairness & input checks
Prelaunch capture · July–October 2026
Not covered
- Solvency, fund custody & withdrawals
- Licensing & regulatory compliance
- Platform & infrastructure security
- Third-party games outside the audit
- Rakeback, rebates & promotions
- Cross-account outcome consistency
- Maximum-win cap enforcement
- KYC, AML & responsible gambling controls
Ongoing verification
Certification requires public launch and a fresh capture of bets through anonymous, self-funded accounts.
The launched build must match the audited implementation. Changes to game rules or payout tables require re-audit.
03Straight answers
The same committed inputs produce the same result.
Every revealed seed was checked against its saved commitment, then each captured result was independently rebuilt from the seed, client seed and nonce.
- 778 commit-reveal epochs checked across all 6 games.
- All 772 next-seed links intact, plus each game’s pre-capture link.
- Player-controlled client seeds and their effect on outcomes tested.
- Card order, mine layouts, Plinko paths, Dice rolls, Limbo results and Keno draws replayed.
39,400 / 39,400 pre-launch bets replayed · 0 mismatches
These results cover the audited pre-launch build and captured inputs. Anonymous public-site capture is still required before certification.
A matching hash establishes consistency with the saved commitment. Keep the commitment before betting; the hash alone does not establish when it was published.
Provisional audit: final certification requires public launch and an anonymous, self-funded recapture with every required check passed.
04The complete public record
Every disclosed finding and re-verified fix stays visible.
- Disclosed findings
- 10
- Games with findings
- 5
- Fixed & re-verified
- 10
05Audit history
The path from pre-launch testing to certification.
- Jul–Oct 2026
Pre-launch audit
Six games independently rebuilt and tested on LIQD’s whitelist environment.
All findings fixed and re-verified
Ten findings remediated across five games before the provisional report.
Provisional report issued
PF-2026-LIQD · Framework v1.1
Provisional · Not yet certified- Pending
Public launch
LIQD opens to the public before the independent live-bet recapture.
- Nov 2026
Anonymous live-bet recapture
After launch · Self-funded accounts and every required dataset check.
- After recheck
Certification pending
Certification is issued only after public launch and a successful independent recapture.
Audit control areas 5/5 passed
- 01PassedSeed, nonce and determinism
- 02PassedRNG and entropy model
- 03PassedLive vs verifier match
- 04PassedGame logic and RTP
- 05PassedFairness integrity
| Control | Evidence | Result |
|---|---|---|
| 01Seed, nonce and determinism | 778 commit-reveal epochs772 next-seed links intact | Pass |
| 02RNG and entropy model | 6 HMAC-SHA256 implementationsPlayer-controlled client seeds | Pass |
| 03Live vs verifier match | 39,400 / 39,400 pre-launch bets matched | Pass |
| 04Game logic and RTP | 6 independent RTP proofs228M simulated rounds | Pass |
| 05Fairness integrity | 201 integrity tests10 findings fixed and re-verified | Pass |
Control results apply to the remediated prerelease environment. All 10 findings from 15 integrity tests were fixed and independently re-verified. Anonymous public bet capture is required before certification.
Audit control areas
5 requirements. Each backed by evidence.
Control results apply to the remediated prerelease environment. All 10 findings from 15 integrity tests were fixed and independently re-verified. Anonymous public bet capture is required before certification.
07Don’t trust the audit. Check it.
Every audit is built so the result can be independently reproduced.
Re-run the audit
Open a game repository and its dataset. Follow its documented setup and reproduction steps.
Have an AI review the code
Open a GitHub review prompt in your AI. Replace [Game] with your game, or tell the AI which game when it asks.
Run the audit on your machine.
Inspect the code. Replay the bets. Challenge the findings.
https://github.com/orgs/ProvablyFair-org/repositories?q=liqd1. Choose a game repository.
2. Follow the repository’s README.
3. Reproduce the published evidence.
6 game repositories · 39,400 captured bets
Reproduce the audit
Clone the code. Replay the bets.
Challenge the findings.
$ git clone https://github.com/ProvablyFair-org/liqd-blackjack$ cd liqd-blackjack# Follow the repository README# Replay the published evidenceVerifier code & captured bets
Simulation harness & findings
6 game repositories · 39,400 recorded bets
Setup and runtime: see each repository’s README
Dispute a result
Check the calculation first. If it still differs, ask us to review it.
Verify a bet
Use your revealed seeds to recreate the round and compare it with your original bet record.
Verify a betRequest review
Send your bet record and calculation details so we can look into the difference.
Request review