From 085bc70e727cfc609c74031b330c1faf48d28a48 Mon Sep 17 00:00:00 2001 From: Shannon Appelcline Date: Tue, 21 Jul 2020 09:19:35 -1000 Subject: [PATCH] light edit as part of 0.20 update --- 10_3_Running_a_Bitcoin_Script_with_P2SH.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/10_3_Running_a_Bitcoin_Script_with_P2SH.md b/10_3_Running_a_Bitcoin_Script_with_P2SH.md index 48f4c0f..955e674 100644 --- a/10_3_Running_a_Bitcoin_Script_with_P2SH.md +++ b/10_3_Running_a_Bitcoin_Script_with_P2SH.md @@ -35,7 +35,7 @@ To unlock this transaction requires that the recipient produce a `scriptSig` tha ### Run the First Round of Validation -The process of unlocking the P2SH transaction then begins with a first round of validation. +The process of unlocking the P2SH transaction then begins with a first round of validation, which checks that the redeem script matches the hashed value in the locking script. Concatenate `scriptSig` and `scriptPubKey` and execute them, as normal: ``` @@ -68,7 +68,7 @@ However, because this was a P2SH script, the execution isn't done. ### Run the Second Round of Validation -For the second round of validation, deserialize the `redeemScript` ("93016387" = "OP_ADD 99 OP_EQUAL"), then execute it using the items in the `scriptSig` prior to the serialized script: +For the second round of validation, verify that the values in the unlocking script satisfy the `redeemScript`: deserialize the `redeemScript` ("93016387" = "OP_ADD 99 OP_EQUAL"), then execute it using the items in the `scriptSig` prior to the serialized script: ``` Script: 1 98 OP_ADD 99 OP_EQUAL