Each verifier reproduces an operator’s documented algorithm. Verified adapters have matched independently captured disclosed rounds with saved seed commitments. Reference adapters implement the published scheme but lack that evidence; historical community examples are identified separately. These labels describe our replay evidence, not a casino endorsement.
Check each tool’s supported algorithm and payout-table scope. Stake includes a payout-table snapshot captured on October 20, 2026; confirm it matches the table used for your bet. A matching seed hash alone does not verify a bet’s outcome.
Not listed?
If an operator isn’t here, we haven’t reproduced its algorithm yet. Want an operator added? Tell us at hey@provablyhero.com.
How to verify a provably fair casino result
A provably fair verifier reproduces a recorded outcome from the inputs used by a supported operator algorithm. It is a check on a particular result, not a prediction of the next result. The process normally requires a disclosed server seed, the client seed attached to the bet and the exact nonce. A saved server seed hash adds the separate commitment check.
Choose the operator before entering data. Similar game names and animations do not establish identical seed formatting, hash functions or outcome conversion. Even when two implementations use the same cryptographic primitive, a different message format can produce a different path. Each verifier page explains the supported algorithm and the evidence behind its status.
Commitment and replay answer different questions
The commitment check hashes the revealed server seed and compares it with the value saved before the result. The replay uses the seed together with the client seed and nonce to reproduce the outcome. A matching seed hash alone does not check the path, and a matching path alone does not establish when a commitment was published.
Keep the original record when you can: operator, game, mode, settings, result, nonce and saved hash. The provably fair guide explains why the time at which a hash was recorded matters. A hash first obtained after disclosure provides less evidence of a precommitted result.
Separate the stages of a fairness check
Check
Evidence needed
What a match means
Seed commitment
Revealed server seed and a previously recorded hash.
The seed matches that saved commitment.
Outcome replay
Client seed, exact nonce and supported algorithm.
The supplied inputs reproduce the computed outcome.
Payout lookup
Rows, risk, applicable table and recorded payout.
The outcome maps to that captured multiplier.
A hash match alone does not verify an outcome. None of these checks is a casino safety certification.
Match the payout configuration as well as the slot
For Plinko, the path leads to a zero-based slot. The payout then comes from the relevant row count, risk and multiplier table. Reproducing a slot is not automatically confirmation that a historical bet used the same table as our captured snapshot, or that the account was settled correctly.
The Plinko verifier directory lists the available adapters. Follow the stated mode restrictions and source dates. An unsupported variant should not inherit the status of a supported one merely because both carry the same operator name.
Handle missing seeds and mismatches carefully
An active seed hash is not the revealed secret seed. If the operator has not disclosed the relevant seed pair, the round cannot be replayed from the hash alone. There is no need to place another bet to use these tools. Existing disclosed examples can be used to understand how a check works.
When a replay differs, first confirm the exact nonce, seed pair, row count and mode. Preserve spelling and case in seeds. Enter a recorded hash in the hash field rather than the server seed field. A mismatch needs investigation of the inputs and supported scope before it supports a claim about an operator. Calculations run locally in your browser; seed inputs are not submitted to our API.
FAQ
Do you store my seeds?
No. Verification runs entirely in your browser; nothing is sent to our servers.
What if the verifier result doesn't match?
First check you used the revealed (not hashed) server seed, the right client seed and the exact nonce. If it still doesn't match, send us the details at hey@provablyhero.com and we'll investigate.
