Where does "six confirmations is safe" come from?
Depositing bitcoin on an exchange often comes with notices like "credited after 3 confirmations" or "6 confirmations required." Confirmations count how many blocks have been built on top of the block containing your transaction, and more of them make reversal harder. But why six, and how different are three and six?
This guide shows by calculation how confirmations relate to the probability of reversal, how that risk changes with an attacker's share of hash power, and how to choose a number of confirmations by amount and compare exchange policies, using hypothetical examples.
What a confirmation means
The Bitcoin Developer Guide explains that a transaction has one confirmation once it is included in a block, and another with each block added on top. Blocks arrive about every ten minutes on average, so six confirmations take about an hour.
More confirmations mean more safety because reversing a transaction requires rebuilding every block from the one containing it up to the present, and producing a longer chain than honest miners have. The more blocks have accumulated, the more work an attacker must catch up on.
How blocks are linked
Each block contains the hash of the previous block, linking them like a chain. Changing one block invalidates every block after it, so an attacker must re-mine all subsequent blocks. Nodes follow the chain with the most accumulated work.
To succeed, an attacker must produce blocks faster than the honest network and close the gap. The Bitcoin whitepaper shows that for an attacker with a minority of hash power, the probability of catching up falls exponentially with the number of blocks behind.
Confirmations and risk, calculated
The table uses the whitepaper's method to estimate the probability of a successful reversal at different confirmation counts, for attackers with 10% or 30% of total hash power.
| Confirmations | Attacker with 10% hash power | Attacker with 30% hash power |
|---|---|---|
| 1 | ≈ 20.5% | ≈ 62.8% |
| 3 | ≈ 1.3% | ≈ 32.5% |
| 6 | ≈ 0.024% | ≈ 13.2% |
| 10 | ≈ 0.0001% | ≈ 4.2% |
Against a small attacker, six confirmations make the risk tiny; against one with 30%, risk remains even at ten. "Six is safe" is a rule of thumb that assumes the attacker is weak.
A hypothetical deposit
How many confirmations to wait for can be judged by weighing the amount against the cost of attack. An attacker who re-mines blocks gives up the rewards those blocks would otherwise have earned, so small amounts are not worth attacking, and larger amounts justify waiting longer.
Here is a hypothetical example: a merchant might accept a coffee-sized payment with one confirmation or even none, while someone receiving the equivalent of hundreds of thousands of dollars would be prudent to wait for six or considerably more. Each confirmation costs about ten minutes of waiting, traded against reduced risk.
Comparing exchange policies
Exchanges set how many confirmations they require before crediting deposits. Policies differ, and an exchange may raise its requirement when network conditions look unusual. Checking the requirement before depositing lets you estimate the wait.
Block intervals average ten minutes but vary considerably, so three confirmations might take fifteen minutes or more than an hour. Looking up the transaction hash in a block explorer shows the current count directly.
The Bitcoin Developer Guide's discussion of transactions also explains why low-fee transactions can wait a long time for their first confirmation. Until that first confirmation arrives, the count has not even started.
A confirmation checklist
When sending or receiving bitcoin, work through these steps.
- Check how many confirmations the recipient, whether an exchange or a counterparty, requires.
- When receiving a large amount, wait for confirmations proportionate to the value before handing over goods or other assets.
- After sending, use a block explorer to check the current confirmation count and fee rate.
- If a low fee leaves the transaction waiting, check whether your wallet supports fee bumping (RBF or CPFP).
- Raise your requirement if network hash power changes sharply or chain reorganizations are reported.
Limits of finality
Bitcoin's finality is probabilistic, so the chance of reversal never reaches exactly zero, though beyond a certain point it becomes negligible in practice. And a confirmed transaction sent to the wrong address or to a scammer cannot be undone. The CFTC warns of fraud risks in virtual currency transactions.
The probabilities come from a simplified model, and the deposit example is hypothetical. When transacting, check your exchange's and wallet's current guidance, paying attention to publication dates, and allow more confirmations as amounts grow.