Commit, Then Reveal
How Provably Fair Mines Actually Works
Provably fair mines runs on a commit-reveal scheme, fixing mine positions before the first click through two seeds and a round counter, and this page walks through what that scheme proves and what it does not.
Provably fair mines is a specific application of a commit-reveal scheme: a way to fix a round's outcome before it starts and let anyone confirm, after the fact, that it was not changed along the way. For a Mines round, that means the mine positions are set before the first click, not chosen as the round unfolds. This page walks through each step of that scheme in order, then covers what it actually proves and what it does not.
- 1
Grid size — usually a 5×5 board of 25 covered tiles, set by the studio, not the player.
- 2
Mine count — chosen before the first click; more mines shrink every safe-tile chance that follows.
- 3
Safe-tile counter — how many uncovered tiles have not been a mine so far in this round.
- 4
Multiplier ladder — the number printed against the current safe-tile count, read off the paytable, not guessed.
- 5
Cash-out step — the moment a player takes what the ladder currently shows, before the next click.
Step one: the server seed and its hash
Before a round begins, the operator's system generates a server seed — a random value it does not reveal yet. Instead of hiding it entirely, the system publishes a cryptographic hash of that seed, visible to the player before the first click. A hash is a one-way transformation: it is easy to compute a hash from a known seed, but effectively impossible to work backward from the hash to guess the seed itself. Publishing the hash first, and the seed later, is what lets a player confirm the seed was not changed after the round already had an outcome.
Step two: the client seed
Mine count set
Chosen once, before the first tile; it fixes every odds figure for the rest of that round.
A tile is clicked
One of the remaining covered tiles is revealed; the round either continues or ends there.
The ladder updates
Each safe click moves the multiplier to the next printed step — the same step for every player who reaches it.
Cash out, or click again
The only two choices at any point: take the current ladder value, or risk it against the next tile.
The player either enters their own client seed or is assigned one automatically, depending on the operator's interface. This second value feeds into the same calculation as the server seed, and because the player controls or at least sees this half of the input, it rules out a scenario where the operator alone could have picked an outcome after seeing how the player was likely to play.
Step three: the nonce
Each round played on the same seed pair is numbered by a nonce, a simple counter that increases by one every round. The nonce keeps every round distinct even when the server seed and client seed stay the same across a session, so round five and round six under identical seeds still produce different mine layouts. Without the nonce, two rounds sharing both seeds would risk producing the identical layout, which is exactly the repetition the counter exists to prevent.
Step four: mine positions, fixed before the first click
Server seed, client seed and nonce are combined through the algorithm into the specific mine positions for that one round of provably fair mines — before the first tile is clicked. This is the core claim the whole scheme exists to support: the layout a player is playing against was already fixed the moment the round began, not adjusted based on which tiles get clicked or when a cash-out looks likely. The mechanics of the round itself, once the grid is live, are covered on mines gambling game.
Step five: rotation and reveal
At some point — often when a player changes their client seed, or after a batch of rounds — the operator reveals the server seed that was in use. At that point anyone can take the revealed server seed, the client seed, and the nonce for any specific round played under that pair, run them through the same publicly known algorithm, and check that the result matches both the mine layout that round actually showed and the hash that was published before play began. That check does not require trusting the operator's own claim about what happened — it only requires the published algorithm and the three revealed inputs.
Recomputing a round yourself
Checking the maths above for one specific round of provably fair mines, rather than trusting that it would check out, is a matter of taking the three inputs — revealed server seed, client seed, nonce — and running them through the documented hashing and mine-placement steps. A full walkthrough of that recomputation, tool by tool, sits on verify a mines round. Terms like server seed, client seed and nonce, along with the rest of the vocabulary used on this page, are each defined in one line on the mines glossary.
What the scheme proves
Provably fair mines proves that the mine positions for a given round were fixed by the seeds before the first click, and that they were not altered after the fact — because the published hash locks in the server seed before play, and the later reveal lets anyone check the seed against that hash. It proves the round's outcome was not adjusted mid-play based on how the player was clicking.
What the scheme does not prove
The scheme says nothing about an operator's own account rules — bet limits, bonus wagering contribution, or what happens to an interrupted round — none of which the seed maths touches at all; those questions are read from an operator's terms instead, covered on mines casino game. It also says nothing about how quickly a withdrawal clears once a round is won, which is an account and payments question entirely separate from the round's fairness. And it says nothing about identity-check requirements, which is where the mines gambling sites ranking's own five criteria come in — a casino can run a fully provably fair Mines round and still print nothing about how it verifies a player's identity, or the reverse.
A provably fair mines game versus a “trust us” game
Not every Mines build publishes enough for a player to check the scheme above. A genuine provably fair mines game shows the server seed's hash before play, lets the player see or set the client seed, and reveals the server seed afterward so the maths can be recomputed. A build that skips any of those three steps is not a provably fair mines game in the sense described on this page, whatever marketing language it uses — the label only means something when all three steps are actually available to check. Where an operator's own interface exposes a seed history with past rounds, past nonces and revealed seeds attached, that is the clearest sign the round in front of you is a provably fair mines game rather than a system asking to be trusted without evidence. Where that history is missing or partial, treat the “provably fair” label as unconfirmed for that specific build until the three steps can actually be checked.