How Do Zero-Confirmation Transactions Increase the Risk of a Double-Spend?

Zero-confirmation transactions are transactions that are broadcast to the network but accepted by a vendor or service before they are included in a block. This increases double-spend risk because the transaction is not yet secured by the blockchain's cryptographic proof-of-work.

An attacker can broadcast a payment transaction and immediately follow it up with a conflicting transaction that sends the same funds back to themselves, which a malicious miner can prioritize.

Can a Validator in a PoS System Execute a Successful Double-Spend without a Majority Stake?
What Is a “Zero-Confirmation” Transaction and What Are Its Inherent Risks?
How Do Zero-Confirmation Transactions Increase the Vulnerability to a Double-Spend?
How Does a Transaction’s Confirmation Status Relate to Double-Spending Risk?
How Does a Race Attack Attempt to Double-Spend Cryptocurrency?
How Do “Zero-Confirmation” Transactions Pose a Risk to Merchants?
How Does Network Congestion Affect Confirmation Time and Double-Spend Risk?
What Is the Difference between a Zero-Confirmation and a One-Confirmation Transaction?

Glossar