Thrill provably fair analysis

Thrill fairness construction: HMAC-SHA512 seed pair (documented) — not the Stake-family SHA-256. Independently verifiable: yes. Client seed: settable. Fairness score 9/10. Snapshot 2026-08-18.

Thrill publishes per-game PF documentation for its Originals: committed server seed, settable client seed, per-bet nonce, HMAC-SHA-512 derivation with game-specific byte conversion, verifiable from transaction history. Declared RTP across Originals runs 98.15–99.48%. Note the construction is SHA-512 — verifiers hard-coded to the Stake-family SHA-256 will not reproduce Thrill rounds.

How to verify a Thrill round

  1. Save the committed server-seed hash (or the published chain/proof values on chain- and VRF-based games) before playing.
  2. Set your own client seed where the scheme supports one.
  3. After the session, rotate the seed pair or open the revealed values; confirm the revealed seed hashes to the commitment.
  4. Recompute the round from the revealed values with the operator’s published per-game formula or our seed verifier.
  5. A mismatch on any single round — after checking encoding and nonce indexing — is the only evidence of tampering that actually means something.

Originals and declared house edge

Verification proves a round was not altered after the bet; the declared edge is applied openly in the payout table and is unaffected by any of this.

GameDeclared edgeNotes
Dice1%
Keno1%
Crash1%
Blackjack0.52%
Limbo1%
Plinko1%
Mines1%
HiLo1%
Slide1.85%98.15% RTP — the weakest original in the Thrill set.

Anomalies and caveats

Anomalies describe observations from public code, documentation or reporting. They are not accusations of cheating; where something is unproven we say so.

Scoring breakdown — 9/10

The score grades the fairness system and its transparency, not the casino overall. It says nothing about licensing, solvency or withdrawal reliability.

Method and sources

Thrill PF documentation as reported by independent reviewers (cryptoslate, btcgosu, cryptolinks — 2026); catalogue edges from our review dataset.

Analysis based on public documentation, community verifiers and — where noted — the operator's public client-side JavaScript, snapshot 2026-08-18. Constructions can change; the date matters.

Other fairness reports