From bc19a4534c4a8cd700ebabcdfd8c9615440105eb Mon Sep 17 00:00:00 2001 From: clenser Date: Thu, 19 Oct 2023 01:37:35 +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 aa6e6872..cbfa2977 100644 --- a/ch06_transactions.adoc +++ b/ch06_transactions.adoc @@ -812,7 +812,7 @@ _circular dependency_. ==== Third-Party Transaction Malleability -A more complex series of transactions can sometimes eliminate a circular +A more ((("transactions", "witnesses", "third-party transaction malleability", id="transaction-witness-third-party")))((("witnesses", "third-party transaction malleability", id="witness-circular-third-party")))((("third-party transaction malleability", id="third-party")))complex series of transactions can sometimes eliminate a circular dependency, but many protocols will then encounter a new concern: it's often possible to solve the same script in different ways. For example, consider our simple script from <>: @@ -872,7 +872,7 @@ transaction fees. This mutates Alice's transaction but only in a way that Alice wants. For that reason, we will occasionally prefix the word _unwanted_ to the term _transaction malleability_. Even when we and other Bitcoin technical writers use the shorter term, we're almost -certainly talking about the unwanted variant of malleability. +certainly talking about the unwanted variant of((("transactions", "witnesses", "third-party transaction malleability", startref="transaction-witness-third-party")))((("witnesses", "third-party transaction malleability", startref="witness-circular-third-party")))((("third-party transaction malleability", startref="third-party"))) malleability. ==== ==== Second-Party Transaction Malleability