diff --git a/8_2_Building_a_Bitcoin_Script_with_P2SH.md b/8_2_Building_a_Bitcoin_Script_with_P2SH.md index 8fb3746..a751987 100644 --- a/8_2_Building_a_Bitcoin_Script_with_P2SH.md +++ b/8_2_Building_a_Bitcoin_Script_with_P2SH.md @@ -13,11 +13,11 @@ In [ยง7.2: Running a Bitcoin Script](7_2_Running_a_Bitcoin_Script.md), we offere To lock this transaction do the following: 1. Serialize `OP_ADD 99 OP_EQUAL` (``) then SHA-256 and RIPEMD-160 hash it (``). - a. OP_ADD = 0x93 - b. 99 = 0x01, 0x63, the first to push one byte onto the stack, the second as the hex translation of 99 - c. OP_EQUAL = 0x87 - d. `` = "93016387" - e. `` = "3f58b4f7b14847a9083694b9b3b52a4cea2569ed" + *. OP_ADD = 0x93 + *. 99 = 0x01, 0x63, the first to push one byte onto the stack, the second as the hex translation of 99 + *. OP_EQUAL = 0x87 + *. `` = "93016387" + *. `` = "3f58b4f7b14847a9083694b9b3b52a4cea2569ed" 2. Save `` for future reference as the `redeemScript`. 3. Produce a P2SH locking script that includes the hashed script (`OP_HASH160 OP_EQUAL`). 4. Create a transaction using that `scriptPubKey`.