Mines is played on a 5 × 5 grid. You choose how many mines are hidden, place a bet and open tiles one by one. Every safe tile raises the cash-out multiplier; one mine ends the round and takes the stake. With money riding on every tap, you need to know the casino cannot move mines mid-round or bias tiles against you. That is what provably fair cryptography is for, the same approach used in crypto Dice, Plinko and Limbo.

The commitment scheme in plain English

  • Server seed: before the round, the casino's server generates a random server seed, which decides the mine layout.
  • Hash disclosure: the server seed is run through a one-way hash function, usually SHA-256, and only the hash is shown to you. A SHA-256 hash is 64 characters long. Because hashing cannot be reversed or faked, the server cannot change the seed without changing the hash.
  • Client seed: your browser or app supplies a client seed, which you can often edit. The two seeds, plus a round counter called a nonce, are combined to fix which of the 25 tiles hide mines.

Think of the hash as a sealed envelope: if the contents change, the seal no longer matches.

How to verify a round, step by step

  1. Copy the server seed revealed when the round ends, or when you rotate to a new seed pair.
  2. Hash it with any SHA-256 tool. Many casinos link one in the game.
  3. Compare the result with the hash you were shown before your first tap.
  4. If it matches, the mine map was fixed from the start.
  5. If it does not match, the round was altered, which is exactly what the system is designed to expose.

Most games wrap these steps in a single Verify button, which works fine in a mobile browser. Knowing the manual process means you do not have to trust that button.

Can the casino change mines during a round?

A common worry is that the game could let you hit a few safe tiles, then move the mines. In a provably fair game that is not possible, because all 25 outcomes are tied to the seed hash you saw before the round. When you open a tile, the game reveals what was already set; it does not roll again. If the casino moved a mine, the revealed seed would no longer produce the layout you played, and the check would fail.

Hash maths in action: a short example

  • Server seed: f9d0…2a1 (hidden until the round ends)
  • SHA-256 hash: cd15bfa…e907 (shown before the round)
  • Client seed: user123
  • Result: the combined seeds produce the mine map. After the round, you hash f9d0…2a1. If you get cd15bfa…e907, the seed was not changed.

Changing even one character of the seed, such as making one letter a capital, produces a completely different hash. That is why any tampering shows up at once.

If you still doubt the numbers

  • Change your client seed each session. The server cannot know it in advance, so it cannot plan a layout around it.
  • Use an independent hash tool, for example openssl dgst -sha256 in a terminal, instead of the casino's own checker.
  • Check for licensing and testing. Play at licensed casinos, and look for independent test reports where the casino or studio publishes them.

Other games with the same fairness system

If you trust the provably fair model in Mines, you will find the same seed and hash system in Dice, Plinko, Limbo, crash games and CoinFlip. Each one fixes the outcome before your bet and lets you verify it afterwards, so once you know the check in one game you can use it across the instant games range.

Fair does not mean profitable

Provably fair maths proves the results were not rigged. It does not tilt the odds your way, and the house edge still applies to every round. Set a stop-loss (for example, 20% of your session bankroll) and a stop-win (for example, bank your stake once you are 50% up), and take breaks, especially when you move from low-mine boards to high-risk ones. Our responsible gaming page lists the limit tools to look for.