From 2f254883eb95400dbbcbc8deefdb918e4a1df0c2 Mon Sep 17 00:00:00 2001 From: Shannon Appelcline Date: Tue, 7 Jul 2020 15:01:00 -1000 Subject: [PATCH] fix importaddress 0.20 does actually allow you to import into a pruned node, you just have to tell it not to rescan! --- 06_2_Spending_a_Transaction_to_a_Multisig.md | 6 +++++- 1 file changed, 5 insertions(+), 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 10fa66f..a70634f 100644 --- a/06_2_Spending_a_Transaction_to_a_Multisig.md +++ b/06_2_Spending_a_Transaction_to_a_Multisig.md @@ -10,7 +10,11 @@ To start with, you need to find your funds; your computer doesn't know to look f ``` $ bitcoin-cli -named importaddress address=2NAGfA4nW6nrZkD5je8tSiAcYB9xL2xYMCz ``` -Here's the catch: you can't do this if you have a pruned node! This command can take a while to run because it does a `rescan` to find all the related transactions. Afterward the funds should show up when you `listunspent` ... but they still aren't easily spendable. (In fact, your wallet may claim they're not `spendable` at all!) +If you've got a pruned node (and you probably do), you'll instead need to tell it no to rescan: +``` +$ bitcoin-cli -named importaddress address=2NAGfA4nW6nrZkD5je8tSiAcYB9xL2xYMCz rescan="false" +``` +Afterward the funds should show up when you `listunspent` ... but they still aren't easily spendable. (In fact, your wallet may claim they're not `spendable` at all!) If you're not able to incorporate the address into your wallet due to pruning, using `gettransaction` to get info instead (or look on a block explorer). ```