1

Given 2 scenarios,

  1. I used the command [addmultisigaddress] to create a multisigaddress using public keys from walletA only. When I run this command [listaddressgroupings], I'm able to see that this address is one of the account in walletA. Running the [validateaddress] command will show that this multisigaddress belongs to walletA.

  2. I used the command [addmultisigaddress] to create a multisigaddress using public keys from walletA and walletB. Let's say 2 public keys from walletA and 1 public key from walletB. When I run this command [listaddressgroupings] for both walletA or walletB, this address is not listed in either of the wallets. Running the [validateaddress] command for both walletA or walletB show that this multisigaddress doesn't belong to either one of them.

  • Can you show a set of example inputs and outputs? – Raghav Sood Aug 7 '18 at 5:29
1

This is (unfortunately) the correct behavior in Bitcoin Core. This is due to how the wallet is structured and what it determines to be part of the wallet.

In order to be able to have the multisig address be "part" of your wallet, you need to import it using importmulti or importaddres. That way it will be added as a watch only address so the wallet will track transactions to and from it.

  • I see. For the first scenario, the multisig address is part of my wallet and I can use sendfrom. So which is the correct way to create a multisig address? – Charles Aug 7 '18 at 7:36

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.