From 2ac73fbad28d29411ac870645556473838d96345 Mon Sep 17 00:00:00 2001 From: clenser Date: Thu, 19 Oct 2023 01:42:26 +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 34d88bd4..79239ab7 100644 --- a/ch06_transactions.adoc +++ b/ch06_transactions.adoc @@ -920,7 +920,7 @@ mutation ((("transactions", "witnesses", "second-party transaction malleability" [[segwit]] ==== Segregated Witness -As early as https://oreil.ly/---bp[2011], +As ((("transactions", "witnesses", "segregated witness", id="transaction-witness-segwit")))((("witnesses", "segregated witness", id="witness-segwit")))((("segregated witness (segwit)", id="segregated-witness-segwit")))early as https://oreil.ly/---bp[2011], protocol developers knew how to solve the problems of circular dependence, third-party malleability, and second-party malleability. The idea was to avoid including the input script in the calculation that @@ -978,7 +978,7 @@ from someone who controlled the private key. To make that system more flexible, the initial release of Bitcoin introduced scripts that allow bitcoins to be received to output scripts and spent with input scripts. Later experience with contract protocols inspired allowing bitcoins to -be received to witness programs and spent with the witness structure. The terms and fields used in different versions of Bitcoin are shown in <>. +be received to witness programs and spent with the witness structure. The terms and fields used in different versions of Bitcoin((("transactions", "witnesses", "segregated witness", startref="transaction-witness-segwit")))((("witnesses", "segregated witness", startref="witness-segwit")))((("segregated witness (segwit)", startref="segregated-witness-segwit"))) are shown in <>. ++++