How Does a Higher Confirmation Requirement Mitigate a Double-Spending Attack?

A confirmation is a block added to the blockchain after the block containing a transaction. Each subsequent block makes it exponentially harder to reverse the transaction, as an attacker would need to rewrite the chain from that point.

By requiring more confirmations (e.g. 50 instead of 6), the exchange ensures the transaction is buried deep in the chain, making a successful reversal via a 51% attack prohibitively expensive and unlikely.

What Is the Role of Confirmation Blocks in Mitigating Double-Spending?
What Is Double-Spending and Why Is a 51% Attack Necessary to Execute It?
How Does Increasing the Confirmation Count Mitigate a Double-Spending Attack?
How Does Increasing the Number of Confirmations Mitigate Double-Spend Risk?
What Is Double-Spending, and Why Is It the Main Concern of a 51% Attack?
How Does Increasing Confirmation Requirements Mitigate Risk?
How Does a Delayed Block Finality Mechanism Help Defend against Double-Spends?
What Is an ‘Orphan Block’ and How Does It Relate to Transaction Confirmation?

Glossar