Update 8_1_Building_a_Bitcoin_Script_with_P2SH.md

This commit is contained in:
Shannon Appelcline 2017-05-17 15:47:06 -07:00 committed by GitHub
parent 049a5070d8
commit 67874becd0

View File

@ -16,6 +16,8 @@ Here's the gotcha for using Bitcoin Scripts: for security reasons, Bitcoin nodes
So how do you write a more complex Bitcoin Script? The answer is in that last sort of standard transaction, the P2SH. You can put any sort of long and complex script into a P2SH transaction, and as long as you follow the standard rules for embedding your script and for redeeming the funds, you'll get all the benefits of Bitcoin Scripting. So how do you write a more complex Bitcoin Script? The answer is in that last sort of standard transaction, the P2SH. You can put any sort of long and complex script into a P2SH transaction, and as long as you follow the standard rules for embedding your script and for redeeming the funds, you'll get all the benefits of Bitcoin Scripting.
> **VERSION WARNING:** Arbitrary (non-standard) P2SH scripts only became standard as of Bitcoin Core 0.10.0. Before that only P2SH Multisigs were allowed.
## Lock a P2SH Transaction ## Lock a P2SH Transaction
You already saw a P2SH transaction when you created a multisig in [6.1: Sending a Transaction to a Multisig](6_1_Sending_a_Transaction_to_a_Multisig.md). Though multisig is one of the standard transaction type, `bitcoin-cli` actually simplifies the usage of its multisigs by embedding them into P2SH transactions, as described more fully in the next section. You already saw a P2SH transaction when you created a multisig in [6.1: Sending a Transaction to a Multisig](6_1_Sending_a_Transaction_to_a_Multisig.md). Though multisig is one of the standard transaction type, `bitcoin-cli` actually simplifies the usage of its multisigs by embedding them into P2SH transactions, as described more fully in the next section.