From 3216c054962db2a1d5014945d1d1773f016750e0 Mon Sep 17 00:00:00 2001 From: clenser Date: Thu, 19 Oct 2023 01:17:39 +0000 Subject: [PATCH] Edited ch06_transactions.adoc with Atlas code editor --- ch06_transactions.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ch06_transactions.adoc b/ch06_transactions.adoc index 2c1c8d04..bf2f800c 100644 --- a/ch06_transactions.adoc +++ b/ch06_transactions.adoc @@ -579,7 +579,7 @@ also sends the signal for opt-in replace by fee ((("transactions", "inputs", sta === Outputs -The outputs field of a transaction contains several fields related to +The ((("transactions", "outputs", id="transaction-output")))((("outputs", id="output-transaction")))outputs field of a transaction contains several fields related to specific outputs. Just as we did with the inputs field, we'll start by looking at the specific bytes of the outputs field from the example transaction where Alice pays Bob, displayed as @@ -723,7 +723,7 @@ script conditions in P2SH redeem script, segwit v0 witness scripts, and segwit v1 (taproot) leaf scripts. We'll look at each of the current standard transaction templates and -learn how to parse scripts in <>. +learn how to ((("transactions", "outputs", startref="transaction-output")))((("outputs", startref="output-transaction")))parse scripts in <>. [[witness_structure]] === Witness Structure