Claim checks
An operator says a number. We do the math in public.
Casinos publish plenty of numbers: “99% RTP”, “max win 1,000×”, “provably fair”. Most players take them on trust. Claim checks don’t. We take one specific, checkable claim, show where it came from, recompute it with the operator’s own table or algorithm, and publish the verdict together with everything you need to rerun the check yourself.
How we check
- Capture the claim. We record the exact wording, where it appears and when, with a dated snapshot.
- Recompute it. With the method that fits: exact calculation from the multiplier table, test vectors from real disclosed rounds, or simulation where exact math isn’t possible.
- Publish the proof. The calculation runs live on the page, with the table version, algorithm version and engine version. If the operator changes the table, we recheck.
Verdicts
| Verdict | Meaning |
|---|---|
| Confirmed | Our calculation matches the claim (allowing for normal rounding). |
| Partially confirmed | Part of the claim holds - for example, only for some row counts or risk levels - or it holds only with a condition the operator doesn’t state. |
| Not confirmed | Our calculation doesn’t match the claim. Published only after a second independent check and after asking the operator for comment. |
| Can’t verify | We don’t have the data to check it yet - for example, the algorithm isn’t documented. |
What claim checks are not
A claim check tests one number or statement. It’s not a verdict on whether a casino is “good”, “safe” or “legit”, and it says nothing about withdrawals, support or licensing unless that’s the claim being checked. Every check ends with a section called What this check doesn’t prove.
Ground rules
- Neutral language: verdicts, not accusations.
- Every check names its sources and dates.
- Operators can send corrections to hey@provablyhero.com; we publish meaningful corrections with a changelog.
The first checks are being prepared. Each will appear here with its verdict, sources and date.