Skip to main content

What Is the Risk of Accepting a Transaction with Zero Confirmations?

The primary risk is a double-spend attack. With zero confirmations, the transaction is only in the memory pool (mempool) and has not been included in a block.

An attacker could broadcast a conflicting transaction with a higher fee to a miner, which could be included in the next block, invalidating the original transaction.

What Are the Specific Conditions That Trigger a Slashing Event?
How Do Exchanges Mitigate the Risk of a Double-Spend Attack?
What Is Transaction Confirmation Time and Why Is It Crucial for Preventing Double-Spends?
What Is a “Race Attack” in the Context of Double-Spending?