arno/bitcoinbook
1
0
Fork 0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2024-12-23 15:18:11 +00:00
Code Issues Releases Wiki Activity

Edited ch02_overview.adoc with Atlas code editor

Browse Source
This commit is contained in:
clenser 2023-10-13 18:08:46 +00:00
parent 0c6536b59d
commit 45a4970720
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
ch02_overview.adoc
View File

@ -343,13 +343,13 @@ while connected to the Bitcoin network.
==== Getting the Right Inputs
Alice's wallet
application will first have to find inputs that can pay the amount she
application ((("inputs", "constructing transactions")))will first have to find inputs that can pay the amount she
wants to send to Bob. Most wallets keep track of all the available
outputs belonging to addresses in the wallet. Therefore, Alice's wallet
would contain a copy of the transaction output from Joe's transaction,
which was created in exchange for cash (see <<getting_first_bitcoin>>).
A bitcoin wallet application that runs on a full node actually
contains a copy of every confirmed transaction's unspent outputs, called
contains a copy of every confirmed transaction's ((("Unspent Transaction Outputs (UTXOs)")))unspent outputs, called
_Unspent Transaction Outputs_ (UTXOs).
However, because full nodes use more resources, many
user wallets run lightweight clients that track only the user's own