arno/bitcoinbook
1
0
Fork 0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2025-03-26 04:15:44 +00:00
Code Issues Releases Wiki Activity

CH02::Bobs view: clarify what Bob's wallet sees (peer vs client)

Browse Source 
Clarify what Bob's wallet can see if it's a lightweight client versus a
full node peer.
This commit is contained in:
David A. Harding 2023-02-04 16:58:13 -10:00
parent fddaace478
commit e338f0ddc7
1 changed files with 4 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
ch02.asciidoc
View File

@ -503,16 +503,12 @@ few seconds.
===== Bob's view
If Bob's bitcoin wallet application is directly connected to Alice's
wallet application, Bob's wallet application might be the first node to
wallet application, Bob's wallet application might be the first to
receive the transaction. However, even if Alice's wallet sends the
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 outputs redeemable by Bob's
an incoming payment because it contains an output redeemable by Bob's
keys. Bob's wallet application can also independently verify that the
transaction is well formed, uses previously unspent inputs, and contains
sufficient transaction fees to be included in the next block. At this
point Bob can assume, with little risk, that the transaction will
shortly be included in a block and confirmed.
[TIP]
====
@ -527,6 +523,8 @@ 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.
=== Bitcoin Mining