What It Actually Proves
The mechanism is a commitment scheme, and it is sound. Before you bet, the house shows you a hash of its server seed. You supply, or accept, a client seed. The outcome is computed from both plus a counter, and the server seed is revealed later so you can recompute the result and check the hash matches.
Because a hash cannot practically be reversed or collided, the house cannot look at your bet and then pick a server seed that produces a bad outcome for you. The commitment was made first. That is a real guarantee, verifiable by you, without trusting anybody. Our step-by-step verification guide covers how to do it.
Everything below is about the boundary of that guarantee.
Gap 1: It Says Nothing About the Edge
This is the largest gap by far, and the least discussed. The proof verifies that a number was drawn honestly. It says nothing whatsoever about what that number pays.
A game can be perfectly provably fair and carry a 15% house edge. The two properties are independent. On a dice or crash game with a published formula the gap is narrow, because the payout rule is simple and public. On a provably fair slot, with a symbol distribution nobody publishes, the gap is enormous: you can verify every draw and still have no idea what the game returns.
SlotDrop reviewWe ran these checks on CashyLicence, terms, withdrawals: what is verified, what is only a claim, and what to test yourself before depositing.Read the Cashy review →Gap 2: Selective Revealing
The commitment binds the house to one server seed — but only if you know which commitment applies to your bet. If an operator generates several server seeds, publishes several hashes, and only later decides which pair to present as "yours", the guarantee weakens.
The defence is that the hash must be shown to you, tied to your session, before you bet, and must not change. Verify that the hash you were shown at the start of the seed period is the one revealed at the end. If a site rotates seeds without letting you see the commitment in advance, the property you are relying on is not there.
Gap 3: Who Wrote Your Client Seed
The client seed exists so that the house cannot control both inputs. On many platforms the default client seed is generated by JavaScript that the operator serves to your browser.
If the operator controls that code, it controls both halves of the input in the default case. There is a straightforward and complete fix, and it takes ten seconds: set your own client seed manually, to something the operator could not have predicted. Every serious provably fair implementation lets you. Almost nobody does it.
Gap 4: Seed Quality
A hash commitment proves the seed was not changed. It does not prove the seed was unpredictable to begin with. If a server seed is derived from a weak source — a timestamp, a counter, a poorly seeded generator — an attacker who works out the pattern can predict outcomes, and every hash will still verify perfectly.
This is not something a player can check. It is what independent code audits are for, and it is the reason "provably fair" and "audited" are not synonyms. Ask which is claimed. Most sites claim the first and let readers assume the second.
Gap 5: The Mapping Step
Between the hash and the outcome sits a conversion: turning a hexadecimal digest into a dice roll, a crash multiplier or a reel position. That conversion can be wrong.
The classic error is modulo bias — taking a hash modulo a range that does not divide evenly, which makes low outcomes very slightly more likely. It is invisible in casual play, it verifies correctly every time, and over millions of bets it is worth money. A player cannot detect it from their own results; only reading the published algorithm can.
Where the algorithm is published in full, this gap is closable by anyone willing to read it. Where it is not, "provably fair" is a claim about a process you are not allowed to see.
The Honest Summary
| Claim | Proved by verification? |
|---|---|
| The outcome was fixed before I bet | Yes |
| The result was not altered afterwards | Yes |
| The house cannot see my bet then choose | Yes, if the hash came first |
| The randomness is genuinely unpredictable | No — needs a code audit |
| The payout rule matches what was advertised | No |
| The game returns the stated RTP | No |
| The operator will process my withdrawal | No |
| The operator is licensed anywhere | No |
Four yeses that no conventional casino can offer, and four noes that matter as much as the yeses. Provably fair solves the problem of the rigged draw. It leaves the problems of the priced paytable, the unaudited generator and the operator who stops answering emails exactly where it found them — and those, in practice, are what actually costs players money.
Play with the math on your side
SlotDrop's free tools show you the real house edge, EV and variance behind every bet — before you place it.
Open the Black Box →Reality check: no strategy on this page turns a negative-expectation game into a positive one. Strategy reduces how much the house takes and how fast your bankroll disappears — it does not guarantee profit. Only ever bet money you can afford to lose entirely.