zero confirmation
A zero-confirmation transaction has been broadcast to the Bitcoin network and is visible in the mempool, but has not yet been included in a block. It carries a risk of double-spend until at least one confirmation is received.
A zero-confirmation transaction, also called an unconfirmed transaction, is one that has been broadcast to the Bitcoin network and accepted by nodes into the mempool but has not yet been included in a block. From the moment a transaction enters the mempool it becomes visible to the network, but it has not yet been sealed into the blockchain and carries no protection against reversal.
The risk specific to unconfirmed transactions is double-spending. Because the transaction has not been written into a block, the sender can attempt to broadcast a conflicting transaction that sends the same funds to a different address with a higher fee. If miners pick up the replacement first, the original transaction may never confirm, effectively cancelling the payment. This risk exists until at least one confirmation has been received, and diminishes further with each subsequent block built on top.
Whether accepting zero-confirmation is reasonable depends on the context and the amount involved. For small in-person transactions where the merchant can monitor the mempool for conflicting transactions, the practical risk is low. For larger amounts, online payments, or situations where goods are delivered digitally and instantly, waiting for at least one confirmation is the norm. Six confirmations is a widely cited threshold for large amounts, reflecting the point at which reversing the transaction would require an impractical amount of computational work. A re-org reaching back six blocks, while theoretically possible, becomes exponentially less probable with each additional block.
Frequently asked questions
Can a zero-confirmation transaction be reversed?
An unconfirmed transaction can potentially be replaced or invalidated before it is included in a block. If the sender broadcasts a conflicting transaction spending the same inputs with a higher fee, miners may include the replacement instead, effectively cancelling the original. This is why zero-confirmation transactions carry more risk than confirmed ones. Once a transaction is included in a block and several more blocks are built on top, reversing it becomes computationally prohibitive.
Why do some businesses accept zero-confirmation payments?
For low-value in-person transactions, the practical risk of a successful double-spend is low. Executing one requires the attacker to broadcast a conflicting transaction and have it mined before the merchant releases the goods. For small purchases the cost of the attack often exceeds the potential gain. Many point-of-sale systems accept zero-confirmation for this reason, sometimes combined with mempool monitoring to detect any conflicting transactions as a basic safeguard.
Why is six confirmations the standard for large amounts?
Six confirmations is a convention established in the early years of Bitcoin. Reversing a transaction buried under six blocks would require an attacker to outpace the honest network across those six blocks, which demands an enormous and sustained share of total mining power. Each additional confirmation multiplies the difficulty of reversal exponentially. The six-confirmation guideline is not a protocol rule but a widely adopted standard that many exchanges and services apply for larger transactions.