arno/bitcoinbook
1
0
Fork 0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2025-03-24 11:25:43 +00:00
Code Issues Releases Wiki Activity

CH02::Bobs view: remove tipbox about unconfirmed safety

Browse Source 
This advice may have been somewhat accurate when the first edition of
this book was published and opt-in replace-by-fee wasn't available, but
that's no longer the case.  And now, especially, with default
replace-by-fee on the probable horizon, there's even less safety in
accepting unconfirmed transactions as final without some type of
secondary protection.
This commit is contained in:
David A. Harding 2023-02-04 16:59:19 -10:00
parent e338f0ddc7
commit a543abe388
1 changed files with 0 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
ch02.asciidoc
View File

@ -509,20 +509,6 @@ transaction through other nodes, it will reach Bob's wallet within a few
seconds. Bob's wallet will immediately identify Alice's transaction as
an incoming payment because it contains an output redeemable by Bob's
keys. Bob's wallet application can also independently verify that the
[TIP]
====
((("confirmations", "of small-value transactions",
secondary-sortas="small-value transactions")))A common misconception
about bitcoin transactions is that they must be "confirmed" by waiting
10 minutes for a new block, or up to 60 minutes for a full six
confirmations. Although confirmations ensure the transaction has been
accepted by the whole network, such a delay is unnecessary for
small-value items such as a cup of coffee. A merchant may accept a valid
small-value transaction with no confirmations, with no more risk than a
credit card payment made without an ID or a signature, as merchants
routinely accept today.((("", startref="Tconstruct02")))
====
transaction is well formed. If Bob is using his own full node, his
wallet can further verify Alice's transaction only spends valid UTXOs.