What a confirmation is, and why your deposit waits for several

Seen is not settled

Send a coin and within a second or two the transaction shows up on a block explorer. It has been broadcast: nodes have it, miners or validators have it in their queue, and the explorer is reporting what it heard. What has not happened yet is the only thing that matters — the network has not agreed that this transaction is part of the ledger.

That agreement happens in blocks. A block is a batch of transactions that one miner or validator proposes and the rest of the network accepts. When your transaction is included in a block, it has one confirmation. When another block is built on top of that one, it has two. The count is simply how deep your transaction is buried under later blocks.

Depth matters because the ledger can, briefly, fork. Two miners find a block at nearly the same moment; the network follows both for a block or two until one chain pulls ahead, and the other is abandoned along with every transaction that was only in it. A transaction with one confirmation can be on the losing side of that. A transaction with six has a chain of six blocks that would all have to be discarded.

Where “six confirmations” comes from

The number is not folklore. Section 11 of the Bitcoin whitepaper works out how likely it is that an attacker controlling some fraction of the network’s hashing power can secretly build a longer chain and replace a transaction buried z blocks deep. The result, for an attacker holding 10% of the network:

Each confirmation cuts the risk by roughly a factor of four at this attacker size. The curve is why “six” became the customary threshold for value at rest: it is the point where the number stops being worth writing down.

Two things to read out of the table. The drop is exponential, so the marginal confirmation is worth most early — going from one to two removes three quarters of the risk, going from five to six removes a quarter of what little is left. And the whole table is about one chain’s block time and security model. Six Bitcoin blocks is about an hour. Six blocks on a chain that produces one every three seconds is eighteen seconds, and means something different.

Why the count differs by coin

Each chain settles differently, so a fixed number of blocks is not a fixed amount of certainty. Roughly, the chains this wallet takes deposits on fall into three groups:

• Proof-of-work chains — Bitcoin, Litecoin. Blocks every ten minutes and two and a half minutes respectively; certainty accumulates with depth exactly as the whitepaper table describes, and reversal is a question of hashing power.
• Fast proof-of-stake chains — Ethereum, Polygon, TRON. Blocks every few seconds, and Ethereum in particular reaches an explicit finality after two epochs, roughly thirteen minutes, past which a block cannot be reverted without validators destroying their own stake. Many confirmations arrive quickly; the meaningful threshold is the finality point.
• Consensus-ledger chains — the XRP Ledger. There is no mining and no competing forks to wait out: validators agree on each ledger in a few seconds and it is final when closed. A single confirmation on XRP is a different animal from a single confirmation on Bitcoin.

So the same house, wanting the same level of certainty, ends up with a different number for each coin. That is what the wallet is showing you.

Why a casino waits at all

A shop that ships a physical good can afford to wait for settlement, because the good does not leave until the money is certain. A casino cannot: the moment a deposit is credited, it can be wagered, and a winning wager pays out in seconds. If the deposit is then reversed by a reorganised chain, the house has paid a real withdrawal against money that no longer exists.

That is exactly the attack the whitepaper table describes, aimed at a house instead of a merchant — deposit, bet, and try to unwind the deposit. The confirmation count is the house choosing how small it wants that probability to be before it takes on the exposure. Waiting is not distrust of you; it is the house declining to gamble on the chain.

What to do while it says waiting

1. Open the transaction in the chain’s explorer — the wallet links each coin to its own (Bitcoin, Etherscan, Tronscan, XRPScan and so on) — and watch the confirmation count climb. If it is climbing, nothing is wrong; it is early.
2. Check the count against the number on the deposit screen. A deposit that has reached it and still shows waiting is worth a message to support with the transaction hash; one that has not is simply not there yet.
3. If the transaction has zero confirmations for a long time on a proof-of-work chain, the fee was probably set too low for current demand. It has not failed — it is queued — and why that happens is its own article.
4. If the explorer cannot find the transaction at all, the problem is upstream of confirmations: check the sending wallet, and check that it went to the right network.

The waiting state is the system working. A house that credited at zero confirmations would be faster and would eventually be robbed by exactly the mechanism above — and the cost of that would find its way back to every player. Where the money sits is the companion piece on what happens after it lands.