From f273262cde18c3114e10d7ecd7c6c32da0bb630c Mon Sep 17 00:00:00 2001 From: wintercooled Date: Fri, 23 Mar 2018 11:12:04 +0000 Subject: [PATCH] Update 06_2_Spending_a_Transaction_to_a_Multisig.md fixed minor typo (I think have changed P2SH from pay-to-script to pay-to-scipt-hash. As I have changed this twice now I just want to check that it wasn't omitting the 'hash' deliberately. --- 06_2_Spending_a_Transaction_to_a_Multisig.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/06_2_Spending_a_Transaction_to_a_Multisig.md b/06_2_Spending_a_Transaction_to_a_Multisig.md index a2ea528..98f40ed 100644 --- a/06_2_Spending_a_Transaction_to_a_Multisig.md +++ b/06_2_Spending_a_Transaction_to_a_Multisig.md @@ -31,7 +31,7 @@ $ bitcoin-cli listunspent ## Set Up Your Variables -When you're ready to spend the funds received by a multisignature address, you're going need to collect a _lot_ of data: much more than you need when you spend a normal P2PKH UTXO. That's in part because the info on the multisig address isn't in your wallet, and in part because you're spending money that was sent to a P2SH (pay-to-script) address, and that's a lot more demanding. +When you're ready to spend the funds received by a multisignature address, you're going need to collect a _lot_ of data: much more than you need when you spend a normal P2PKH UTXO. That's in part because the info on the multisig address isn't in your wallet, and in part because you're spending money that was sent to a P2SH (pay-to-script-hash) address, and that's a lot more demanding. In total, you're going to need to collect three things: extended information about the UTXO; the redeemScript; and all the private keys involved. You'll of course need a new recipient address too. The private keys need to wait for the signing step, but everything else can be done now.