From 32afaef9a7ef90b0a582daf9aafb514c1dbaac49 Mon Sep 17 00:00:00 2001 From: rating89us <45968869+rating89us@users.noreply.github.com> Date: Wed, 24 Feb 2021 18:23:26 +0100 Subject: [PATCH] ch07: add roles of sender and recipient --- ch07.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ch07.asciidoc b/ch07.asciidoc index 74b3d70f..bdd0cf4f 100644 --- a/ch07.asciidoc +++ b/ch07.asciidoc @@ -112,7 +112,7 @@ P2SH was developed to resolve these practical difficulties and to make the use o | Unlocking Script | Sig1 Sig2 |======= -As you can see from the tables, with P2SH the complex script that details the conditions for spending the output (redeem script) is not presented in the locking script. Instead, only a hash of it is in the locking script and the redeem script itself is presented later, as part of the unlocking script when the output is spent. This shifts the burden in fees and complexity from the sender to the recipient (spender) of the transaction. +As you can see from the tables, with P2SH the complex script that details the conditions for spending the output (redeem script) is not presented in the locking script. Instead, only a hash of it is in the locking script and the redeem script itself is presented later, as part of the unlocking script when the output is spent. This shifts the burden in fees and complexity from the sender (who creates the transaction) to the recipient (who unlocks and spends the transaction). Let's look at Mohammed's company, the complex multisignature script, and the resulting P2SH scripts.