From 60f88a3463b63703c048135e27f52688eaa96ce0 Mon Sep 17 00:00:00 2001 From: Shannon Appelcline Date: Wed, 17 May 2017 16:17:59 -0700 Subject: [PATCH] Update 8_2_Creating_Multisig_Scripts.md --- 8_2_Creating_Multisig_Scripts.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/8_2_Creating_Multisig_Scripts.md b/8_2_Creating_Multisig_Scripts.md index e6e4612..180ba0e 100644 --- a/8_2_Creating_Multisig_Scripts.md +++ b/8_2_Creating_Multisig_Scripts.md @@ -12,6 +12,8 @@ Multisig transactions are created in Bitcoin using the `OP_CHECKMULTISIG` code. _What is a consensus rule?_ These are the rules that the Bitcoin nodes follow to work together. In large part they're defined by the Bitcoin Core code. These rules include lots of obvious mandates, such as the limit to how many Bitcoins are created for each block and the rules for how transactions may be respent. However, they also include fixes for bugs that have appeared over the years, because once a bug has been introduced into the Bitcoin codebase, it must be continually supported, lest old Bitcoins become unspendable. The extra-pop bug in OP_CHECKMULTISIG is one of the most obvious consensus rules of this sort. Because the original version of OP_CHECKMULTISIG accidentally popped an extra item off the stack, Bitcoin must forever follow that rule, lest complex redemption scripts accidentally be broken, rendering coins unredeemable. Recent versions of Bitcoin core require that leading constant, which is not used, be a "0". +### Lock a Multisig Transaction + The multisig in ยง6.1 was a 1-of-2 multisig built from `$address1` and `$address2`. the resultant `scriptPubKey` would appear as follows: ``` 1 $address1 $address2 2 OP_CHECKMULTISIG