From b9c793cbf191e88e32bd35a008fcd58e1b453ddd Mon Sep 17 00:00:00 2001 From: "judymcconville@roadrunner.com" Date: Sun, 30 Apr 2017 10:31:09 -0700 Subject: [PATCH] Edited ch06.asciidoc with Atlas code editor --- ch06.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ch06.asciidoc b/ch06.asciidoc index ac94ce32..71d4bfe6 100644 --- a/ch06.asciidoc +++ b/ch06.asciidoc @@ -167,7 +167,7 @@ Here are some hints: [[tx_inputs]] ==== Transaction Inputs -((("transaction", "outputs and inputs", "input components")))((("outputs and inputs", "input components")))Transaction inputs identify (by reference) which UTXO will be consumed and provide proof of ownership through an unlocking script. +((("transaction", "outputs and inputs", "input components")))((("outputs and inputs", "input components")))((("unspent transaction outputs (UTXO)")))((("UTXO sets")))Transaction inputs identify (by reference) which UTXO will be consumed and provide proof of ownership through an unlocking script. To build a transaction, a wallet selects from the UTXO it controls, UTXO with enough value to make the requested payment. Sometimes one UTXO is enough, other times more than one is needed. For each UTXO that will be consumed to make this payment, the wallet creates one input pointing to the UTXO and unlocks it with an unlocking script.