Why the casino waits for confirmations

You send a deposit, and the cashier shows something like “waiting for network confirmation”. It is easy to read that as the casino being slow. It is not: the casino is waiting for the chain to make your transfer expensive to undo.

What a confirmation is

Your transfer is broadcast, picked up, and included in a block. That inclusion is the first confirmation. Every block built on top of that one is another confirmation. Nothing about your transfer changes as the count rises — what changes is how much work an attacker would have to redo to produce a competing history in which your transfer never happened.

So “three confirmations” is not a progress bar. It is a threshold the operator has chosen as the point where reversing the deposit stops being realistic.

Why the number is different everywhere

Three variables move it, and all three are the operator's call:

The asset

Chains differ in how fast they produce blocks and how readily a recent block can be displaced. A threshold that is cautious on one chain is reckless on another, so the number is set per asset rather than once for the cashier.

The amount

Many operators credit small deposits at a lower threshold than large ones, because the cost of being wrong scales with the amount while the cost of making you wait does not.

Their own risk appetite

Two operators on the same chain can legitimately pick different numbers. Neither is wrong; one is more cautious.

This is also why the question “how many confirmations does a crypto casino need?” has no single answer, and why anyone who gives you one number for all of them is guessing.

When the count has stopped moving

A stalled confirmation count usually means one of two things, and they have opposite fixes.

The transfer is not in a block yet. It is in the mempool, waiting, because the fee you attached is below what the network is currently clearing. Nothing is lost and nothing is wrong; it is queued. Some wallets can replace it with a higher fee, or you can wait for the congestion to clear.

The transfer is in a block and the casino has not credited it. Now the count is irrelevant: the chain has done its part, and the gap is on the operator's side. That is a support ticket, with the hash. If the count is above their published threshold and the balance has not moved, say exactly that.

A third possibility is worth naming because it is mistaken for the other two: the transfer settled on a chain the casino does not watch, in which case the confirmation count can be perfect and the deposit will never arrive. That case has its own piece.

What confirmations do not protect

Confirmations protect the casino from a reversed deposit. They do nothing for you. In particular, a confirmed deposit is not a promise that the money can leave again: that is governed by the account's terms, its verification state and the withdrawal rules of the rail, which are a different subject with a different section.

Nor do confirmations have anything to do with whether the games are fair. That is what the provably fair scheme is for, and what it proves is narrower than it sounds.

The practical version

Before the first deposit at a new cashier, find the operator's stated threshold for your asset. After you send, check the explorer once rather than the cashier repeatedly: the explorer tells you whether the transfer is queued or settled, and that single fact decides whether you are waiting on the network or on the operator. Everything else follows from knowing which of the two it is.