mirror of
				https://github.com/ChristopherA/Learning-Bitcoin-from-the-Command-Line.git
				synced 2025-10-31 02:17:24 +00:00 
			
		
		
		
	Merge pull request #403 from csralvall/fix-10_4
Fix typos and links in chapter 10.4
This commit is contained in:
		
						commit
						8c4f6bb931
					
				| @ -10,7 +10,7 @@ Multisig transactions are created in Bitcoin using the `OP_CHECKMULTISIG` code. | |||||||
| 2. Pop "n" values from the stack as Bitcoin addresses (hashed public keys). | 2. Pop "n" values from the stack as Bitcoin addresses (hashed public keys). | ||||||
| 3. Pop the next value from the stack (`<m>`). | 3. Pop the next value from the stack (`<m>`). | ||||||
| 4. Pop "m" values from the stack as potential signatures. | 4. Pop "m" values from the stack as potential signatures. | ||||||
| 5. Pop an `0` from the stack due to a mistake in the original coding. | 5. Pop a `0` from the stack due to a mistake in the original coding. | ||||||
| 6. Compare the signatures to the Bitcoin adddresses. | 6. Compare the signatures to the Bitcoin adddresses. | ||||||
| 7. Push a `True` or `False` depending on the result. | 7. Push a `True` or `False` depending on the result. | ||||||
| 
 | 
 | ||||||
| @ -22,11 +22,11 @@ The requirement for that `0` as the first operand for `OP_CHECKMULTISIG` is a co | |||||||
| 
 | 
 | ||||||
| ## Create a Raw Multisig  | ## Create a Raw Multisig  | ||||||
| 
 | 
 | ||||||
| As discussed in [§10.2: Building the Structure of P2SH](10_2_Building_the_Structure_of_P2SH.md), multisigs are one of the standard Bitcoin transaction types. A transaction can be created with a locking script that uses the raw `OP_CHECKMULTISIG` command, and it will be accepted into a block. This is the classic methodology for using multisigs in Bitcoin. | As discussed in [§10.1: Understanding the Foundation of P2SH](10_1_Understanding_the_Foundation_of_P2SH.md), multisigs are one of the standard Bitcoin transaction types. A transaction can be created with a locking script that uses the raw `OP_CHECKMULTISIG` command, and it will be accepted into a block. This is the classic methodology for using multisigs in Bitcoin. | ||||||
| 
 | 
 | ||||||
| As an example, we will revisit the multisig created in [§8.1](08_1_Sending_a_Transaction_to_a_Multisig.md) one final time and build a new locking script for it using this methodology. As you may recall, that was a 2-of-2 multisig built from `$address1` and `$address2`.  | As an example, we will revisit the multisig created in [§6.1](06_1_Sending_a_Transaction_to_a_Multisig.md) one final time and build a new locking script for it using this methodology. As you may recall, that was a 2-of-2 multisig built from `$address1` and `$address2`.  | ||||||
| 
 | 
 | ||||||
| As as `OP_CHECKMULTISIG` locking script requires the "m" (`2`), the addresses, and the "n" (`2`), you could write the following `scriptPubKey`: | As `OP_CHECKMULTISIG` locking script requires the "m" (`2`), the addresses, and the "n" (`2`), you could write the following `scriptPubKey`: | ||||||
| ``` | ``` | ||||||
| 2 $address1 $address2 2 OP_CHECKMULTISIG | 2 $address1 $address2 2 OP_CHECKMULTISIG | ||||||
| ``` | ``` | ||||||
|  | |||||||
		Loading…
	
	
			
			x
			
			
		
	
		Reference in New Issue
	
	Block a user