Skip to content

Commit 5746b96

Browse files
authored
Fix link and file name
Link redirected to 404, and since 10_1 isn't about building, I'm assuming the correct one to link to is 10_2: Building the Structure of P2SH.
1 parent e515da4 commit 5746b96

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

10_4_Scripting_a_Multisig.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ The requirement for that `0` as the first operand for `OP_CHECKMULTISIG` is a co
2222
2323
## Create a Raw Multisig
2424

25-
As discussed in [§10.1: Building a Bitcoin Script with P2SH](10_1_Building_a_Bitcoin_Script_with_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.
25+
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.
2626

2727
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`.
2828

0 commit comments

Comments
 (0)