Provably fair books

Verifiable game logic - and its exact boundaries

Provably fair is the strongest honesty instrument in the crypto-gambling toolbox, and the most oversold one. What it delivers: outcomes that you can recompute from committed seeds - a mathematical check that the game did what it says. What it does not deliver: any statement about the sportsbook's odds, the operator's solvency, or whether the stated edge is one you should pay. 14 tracked books run the in-house games; this page shows the loop, the boundaries and the tools.

The loop, step by step

Live values from our database - details and caveats in each review. "-" = not documented by the operator. "Visit" links may be affiliated.

1. Commitment. The site publishes a hash of the hidden server seed

before you play [1] - hash-locking the game's randomness in advance.

1. Your input. You set (or receive) a client seed and a nonce per

bet [2] - your input prevents pre-computed sequences.

1. Derivation. The outcome is a hash-chain derivation from the two

seeds plus the nonce - HMAC constructions are the common scheme [2].

1. Recompute and verify. On seed rotation the server seed is

revealed; you hash it against the commitment, recompute any historic roll, and compare with what was credited. The verifier tool runs this in your browser for the documented schemes - nothing leaves the page.

Shuffle's help center documents a live scheme openly [4] - the format the reviews use as the reference standard when quoting each book's specifics.

The two boundaries that matter

1. The sportsbook boundary. Match results come from tournaments; the

sportsbook's prices are market products. Nothing about odds quality, feed latency or market honesty is provable from game seeds. The odds guide carries the market-side verification (sampled margins, dated).

1. The parameters boundary. Verification proves the rolls match the

stated derivation - not that the edge is small or the payout table generous. A provably fair 1% edge is a provable 1% tax. The house-edge tool and the market-margin tool price the parameters.

The operator boundary is the third: game-logic honesty says nothing about solvency - the license facts, red flags and payout evidence in each review cover that axis.

What to check before trusting a scheme

• The commitment order. The seed hash must be published before play

[1] - a scheme that reveals seeds first and commitments later is theater.

• The derivation documentation. The exact hash chain, in writing,

with the algorithm named - schemes without documentation are not verifiable, whatever the badge says.

• The rotation interval. Seeds rotate on a schedule you can observe;

rotation is when historic verification becomes possible.

• The verifier support. The site's verifier runs the documented

schemes - if a book's scheme is exotic and unsupported, the honest answer is that you cannot check it here.

Warnings

• The badge is not the scheme. "Provably fair" logos prove nothing

without the derivation documentation; the reviews quote each site's specifics with dates.

• In-house games carry in-house margins. The originals are the

operator's own products - check the edge and payout table before playing, same as every market.

• The casino-lane gravity. Provably fair originals sit beside the

esports product at these books - the bankroll-discipline rules from the betting-cost tool apply to the originals lane with full force.

• The naming trap. Some sites label third-party-provider games

"provably fair" on the provider's behalf - the reviews distinguish first-party schemes from provider claims.

The verification walkthrough, once for real

The abstract loop becomes concrete in one worked pass - the recommended first-verification on any new site:

1. Capture the commitment. Note the published server-seed hash

before playing - the timestamped record is what later verification compares against [1].

1. Set your client seed deliberately. Not the random default -

a seed you chose proves you supplied input [2].

1. Play a session under one seed/nonce sequence. Note each nonce

and outcome.

1. Rotate and reveal. Trigger the seed rotation, get the revealed

server seed.

1. Recompute. Hash the revealed seed against the commitment, then

derive each round from (server seed, client seed, nonce) [2] - the verifier tool does the arithmetic in the browser.

1. Compare. Every derived outcome must match what was credited.

Any mismatch is the end of the relationship, not a support ticket.

One pass through this loop converts "provably fair" from a badge into a verified fact - and it is the cheapest diligence in the sector.

The scheme-failure red flags

Documentation quality separates real schemes from theater:

• No derivation published. A "provably fair" page without the

exact hash chain is unverifiable by definition.

• Reveal-before-commit. Commitments published after play are

decoration [1].

• Provider-label borrowing. First-party games labeled with a

provider's scheme - the reviews distinguish them.

• Closed verification. Verification that requires trusting a

server-side checker is not verification - the recompute must run where you can see it.

The provably-fair market context, stated

The originals lane exists because it is profitable and marketable - the honest market context:

1. The badge's commercial value. "Provably fair" converts

trust-scarce players at near-zero cost - which is why the badge is everywhere and the documentation is not. The documentation IS the product; the badge is its marketing.

1. The margin reality. In-house games run in-house margins -

1%-class dice edges are common, casino-grade multiples exist on the crash class. The house-edge tool prices both before any session.

1. The cross-sell structure. The originals sit beside the

sportsbook at these books - the sportsbook's fine print (bonus restrictions, abuse clauses) applies to the combined account; the bonus hub documents which.

The verifier's honest limitations

The tool verifies the documented schemes - and says so:

• Scheme coverage. The documented families (HMAC chains, hash-

chain crash) - exotic proprietary derivations are out of scope and flagged as such.

• Input accuracy. Verification is only as good as the seeds and

nonces you capture - copy errors produce false mismatches; the verifier's receipt mode records what it checked.

• Scope boundary. Game logic only - the operator's solvency, the

sportsbook's prices and the payout lane are separate axes with their own pages.

The tool exists to make the loop from the verification section a minutes-not-hours exercise - and to make the difference between "documented" and "verified" a routine check rather than a research project.

The provably-fair wrap, and the honest use case

The lane's honest use case in one paragraph: provably fair is a verification standard, not a safety guarantee - the schemes verify game logic, the parameters decide value, the operator risks are untouched. The books that run it well publish derivations and rotate seeds on schedule; the books that badge it carry the reviews' dated specifics.

That honesty is the page's product: the verifier tool runs the documented schemes in your browser, the provably-fair guide carries the full technical walkthrough, and the house-edge and market-margin tools price the parameters the schemes do not cover - everything else on this page is context for verifying honestly.

The verifier session, once on your main book

The recommended routine, on the book you actually play:

1. Capture the commitment before your next session - the

timestamped hash.

1. Set a deliberate client seed for the session - your input,

recorded.

1. Play the session under the recorded seed/nonce sequence.
2. Rotate the seed at the session's end.
3. Recompute in the verifier - the [verifier tool]

(/tools/provably-fair-verifier/) runs the schemes in the browser.

1. File the receipt - the verifier's receipt in the

journal: your own verification record, building with every session.

The routine costs minutes per session and converts the scheme from the site's claim into your record - the honest end state of "provably fair" as a feature.

Where to go next

100% of the tracked books run the games and ~16 coins is the median cashier width; the books table filters on provably fair live, the verifier tool runs the schemes, and the provably fair guide carries the full technical walkthrough.