flywithu/Learning-Bitcoin-from-the-Command-Line
1
1
Fork 0
mirror of https://github.com/ChristopherA/Learning-Bitcoin-from-the-Command-Line.git synced 2025-06-08 08:26:17 +00:00
Code Issues Releases Wiki Activity

Update 8_3_Running_a_Bitcoin_Script_with_P2SH.md

Browse Source
This commit is contained in:
Shannon Appelcline 2017-05-31 11:00:27 -07:00 committed by GitHub
parent eb27be91a3
commit 07fa2ac384
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
8_3_Running_a_Bitcoin_Script_with_P2SH.md
View File

@ -2,7 +2,7 @@
> **NOTE:** This is a draft in progress, so that I can get some feedback from early reviewers. It is not yet ready for learning. > **NOTE:** This is a draft in progress, so that I can get some feedback from early reviewers. It is not yet ready for learning.
Now that you know the theory behind P2SH addresses, you're ready to turn a non-standard Bitcoin Script into an actual transaction. We'll be doing so with our simple locking script from [§7.2: Running a Bitcoin Script](7_2_Running_a_Bitcoin_Script.md), `OP_ADD 99 OP_EQUAL`. Now that you know the theory and practice behind P2SH addresses, you're ready to turn a non-standard Bitcoin Script into an actual transaction. We'll be reusing the simple locking script from [§7.2: Running a Bitcoin Script](7_2_Running_a_Bitcoin_Script.md), `OP_ADD 99 OP_EQUAL`.
## Create a P2SH Transaction ## Create a P2SH Transaction
@ -14,14 +14,14 @@ To lock a transaction with this Script, do the following:
* No worries about endian conversion because it's only one byte * No worries about endian conversion because it's only one byte
3. OP_EQUAL = 0x87 — a simple opcode translation 3. OP_EQUAL = 0x87 — a simple opcode translation
4. `<serialized99Equal>` = "93016387" 4. `<serialized99Equal>` = "93016387"
2. SHA-256 and RIPEMD-160 hash the serialized script. 2. Save `<serialized99Equal>` for future reference as the `redeemScript`.
1. `<hashed99Equal>` = "3f58b4f7b14847a9083694b9b3b52a4cea2569ed"
3. Save `<serialized99Equal>` for future reference as the `redeemScript`.
1. `<redeemScript>` = "93016387" 1. `<redeemScript>` = "93016387"
3. SHA-256 and RIPEMD-160 hash the serialized script.
1. `<hashed99Equal>` = "3f58b4f7b14847a9083694b9b3b52a4cea2569ed"
4. Produce a P2SH locking script that includes the `<hashed99Equal>`. 4. Produce a P2SH locking script that includes the `<hashed99Equal>`.
1. `scriptPubKey` = "a9143f58b4f7b14847a9083694b9b3b52a4cea2569ed87" 1. `scriptPubKey` = "a9143f58b4f7b14847a9083694b9b3b52a4cea2569ed87"
You can then create a transaction using that `scriptPubKey`, probably via an API. You can then create a transaction using this `scriptPubKey`, probably via an API.
## Unlock the P2SH Transaction ## Unlock the P2SH Transaction