arno/bitcoinbook
1
0
Fork 0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2024-12-23 15:18:11 +00:00
Code Issues Releases Wiki Activity

Edited ch06_transactions.adoc with Atlas code editor

Browse Source
This commit is contained in:
clenser 2023-10-19 01:37:35 +00:00
parent 4c37fef517
commit bc19a4534c
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
ch06_transactions.adoc
View File

@ -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 <<witness_structure>>:
@ -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