Every round verifiable by the player, the operator, and the regulator.
Provably fair gaming publishes a fingerprint of a round's randomness before the bet and the randomness itself after it, so anyone can check the outcome was fixed in advance. neoProof™ does this with commit-reveal, certified RNG, and on-chain VRF behind one contract, and anchors every round to a public chain. No player holds a token, so it runs under your existing gaming authorisation, including in US states where digital assets are not permitted.
Round rnd_48201 · verification
SealedBefore the bet is accepted
100%
Of rounds hash-anchored
< 1s
To verify any past round
3
Randomness modes, per game type
7 years
Verifiable round retention
The operator commits before the bet, and proves it after
Publish a fingerprint of the randomness before anyone bets, then publish the randomness itself afterwards. If the two match, the outcome could not have been chosen once the stake was known.
Before the bet
The server seed is committed and sealed
The platform generates a server seed, hashes it, and publishes the hash before any bet is accepted. The seed stays sealed. Changing the seed later would change the hash, and the hash is already on the record.
At the bet
The player contributes entropy
A client seed, chosen by the player or generated in their browser, is combined with an incrementing nonce. The operator cannot predict the player's seed, and the player cannot see the server's.
At settlement
The seed is revealed
Once the round closes, the server seed is published. Anyone can hash it and confirm it matches the commitment issued before the bet.
Any time after
Anyone recomputes the outcome
Hashing the server seed, client seed, and nonce together reproduces the result. A player, your compliance team, or a regulator arrives at the same number without access to your systems.
Three sources of randomness, and when each one is right
A certified RNG fits most casino content. Commit-reveal earns its cost where players expect to check the maths themselves. VRF is worth its latency only for large draws. We will tell you which one your content needs.
| Attribute | Certified RNG | Commit-reveal | On-chain VRF |
|---|---|---|---|
| Source of randomness | Hardware-seeded CSPRNG | Server seed + player seed | Verifiable random function |
| Player verifies independently | No, relies on the certificate | Yes, after reveal | Yes, on-chain |
| Latency added per round | None | ~2ms | 2–30s |
| Cost per round | None | Negligible | Chain fee |
| Regulator position | GLI-19/33, accepted everywhere | Accepted alongside certified RNG | Reviewed case by case |
| Typical use | All certified casino content | Crash, dice, instant, AI dealer | Jackpot draws, tournaments |
A log nobody can rewrite, including us
Every round is hashed and chained to the one before it, so altering any entry breaks every hash that follows. Chains are batched into a Merkle root and anchored to a public chain on a fixed cadence. If a round were edited later, the anchor would no longer match, and anyone checking would see it.
- Hash-chained rounds, Merkle-batched, anchored hourly by default
- Only roots and hashes published, never player data or amounts
- Verifiable for seven years, independent of our infrastructure
Round log → public anchor
every 60s1,450
rounds in batch
7 years
verifiable retention
< 1s
to verify a round
The mechanism behind the neoDealer™ audit promise
Regulators receive a deterministic audit stream for every AI-dealt hand: seed, outcome, render hash, and dealer transcript. A generative dealer has no physical shoe and no pit boss, so every hand anchors the same four artefacts and a regulator can replay any hand from them.
Seed pair
Commitment issued before the deal, seed revealed after. The hand could not be altered once the stake was known.
Outcome
The dealt result, recomputable from the seed pair and nonce by anyone holding the evidence bundle.
Render hash
A fingerprint of the frames actually shown to the player, so the visual matches the settled result.
Dealer transcript
What the AI croupier said, in the player's language, tied to the same round ID.
Three audiences, one record, no privileged access
Each surface below reads the same anchored record. What changes is the scope and the format.
Public round checker
Any player pastes a round ID and sees the commitment, the revealed seed, the recomputation, and the anchor transaction. No account or login is needed.
Regulator portal
A read-only view scoped to one brand: search by round, player, or window, export a signed evidence bundle, and confirm every anchor against the public chain.
Evidence bundles
A single export containing the round log, seed pair, outcome, render hash, anchor transaction, and Merkle path. This is the format our compliance team hands to a regulator during an audit.
What blockchain does not fix
Each of the following is a real boundary, and each has a separate control that addresses it.
It does not certify your game maths
RTP, paytables, and hit frequency are certified by a test house. Anchoring proves a round happened exactly as recorded and says nothing about the paytable behind it. You need both, and GLI-19/33 covers the second.
It does not replace RNG certification
Every regulated market we serve requires a certified RNG. Commit-reveal is additive: it gives the player a check they can run themselves, on top of the certificate.
It does not protect a compromised client
If a front end lies about what it submitted, the chain records the lie. Client integrity is a separate control: code signing, attestation, and server-side validation.
It does not make disputes disappear
It makes the evidence indisputable. Someone still has to read the record and make a decision. What changes is that nobody can argue about what the record says.
A module you can bolt onto a platform you already run
neoProof integrates against an existing PAM as a REST and webhook module. You post round data; we return commitments, anchor the logs, and expose the verifier. No migration, no wallet change, and no dependency on the rest of the platform.
// 200 OK, issued before the bet was accepted{ "round_id": "rnd_48201", "commitment": "0x9f3c7d1e...7ae1", "algorithm": "sha256", "committed_at": "2026-08-17T09:14:22.041Z", "server_seed": null}Commitment before acceptance
The API refuses a bet on a round with no published commitment. The guarantee is enforced by the contract.
Idempotent anchoring
Re-posting a round that is already anchored returns the existing proof instead of creating a second record.
Bring your own game content
Round records from any provider can be anchored. Full commit-reveal applies to our own content, where we control the generator.
Exportable evidence
Every bundle is a signed, self-contained file a regulator can verify offline with published tooling.
Questions operators ask before running neoProof
No. Every regulated market we operate in requires a certified RNG, and neoProof runs on top of it. The certificate tells a regulator the generator is sound. The commitment tells the player this round was not altered after they bet. Regulators expect both.
See the verifier running on your round data
A 45-minute session with a solutions architect: which of your games support full commit-reveal, what anchoring costs at your volume, and what the evidence bundle looks like in the format your regulator asks for.