From 45a4970720c0b1877be418c44fd9a924051b55c4 Mon Sep 17 00:00:00 2001 From: clenser Date: Fri, 13 Oct 2023 18:08:46 +0000 Subject: [PATCH] Edited ch02_overview.adoc with Atlas code editor --- ch02_overview.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ch02_overview.adoc b/ch02_overview.adoc index 2fb13f27..19ed9198 100644 --- a/ch02_overview.adoc +++ b/ch02_overview.adoc @@ -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 <>). 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