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-10-31 02:17:24 +00:00
Code Issues Releases Wiki Activity

Update 8_1_Understanding_the_Foundation_of_P2SH.md

Browse Source
This commit is contained in:
Shannon Appelcline 2017-05-24 13:40:55 -07:00 committed by GitHub
parent 5b64303b1d
commit 256dc432f8
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
8_1_Understanding_the_Foundation_of_P2SH.md
View File

@ -78,6 +78,18 @@ You create hexcode by stepping through your locking script and turning each elem
* Larger constants are translated into 0x01 to 0x4e (OP_PUSHDATA, including a specification of how many bytes to push)
* Operators are translated to the matching byte for that opcode
The constants are the most troublesome part. Often you'll need to translate decimals into hexidecimals. This can be done with the `printf` command:
```
$ decimal=1546288031
$ hex=(printf '%x\n' $decimal)
$ echo $hex
5c2a7b9f
```
And you'll always need to know the size of your constants. You can just remember that every two hexidecimal characters is one byte. Or, you can use `echo -n` piped to `wc -c`, and divide that in two:
```
user1@blockstream:~$ echo -n $hex | wc -c
8
```
#### Create the Hex Code: A Multisig Example
It may be easier to understand this by taking an existing hexcode and translating it back to Bitcoin Script. For example, look at the `redeemScript` that you used [§6.1](6_1_Sending_a_Transaction_to_a_Multisig.md):