What can 1 master public key in a multisig reveal?

What can 1 master public key in a multisig reveal?

Assume you have the following situation: You are going to create a new multisig wallet with Electrum. 2 signatures are from old hardware wallets and 1 signature is brand new.

The new multisig will only be used with Electrum and Electrum personal server connected to Bitcoin Core. The 2 old signatures from the hardware wallets has been used with the hardware wallets own wallets (like Ledger Live and Trezor Wallet). Then I guess we can assume that the master public keys from those 2 wallets has been uploaded to some server somewhere and could be "leaked".

From a privacy standpoint, if I create a new multisig, is it possible to get any information from the 2 old master public keys? Or, do you need all 3 keys?

Would it be a good practice to create two new master public keys (by "reinstalling" the old hardware wallets) and create a new multisig with 3 brand new keys (and treat them with more care in the future)? Or is it fine, because 1 key is new?

https://ift.tt/2GV5nym

Comments

Post a Comment

Popular posts from this blog

sendrawtransaction and txn-mempool-conflict

sendrawtransaction and txn-mempool-conflict When i sendrawtransaction to bitcoind, i get error (exceptions) 18: txn-mempool-conflict (use Bitcoin JSON-RPC denpamusic/php-bitcoinrpc ) But the transaction is sent to the network and is subsequently confirmed. Example one decoded transaction : https://jsfiddle.net/rn58a4j6/ then i send this transaction: 94ec12fc463230b4285a29b047608627c05572a4c6eabe6688a201ce49ae72f7 https://ift.tt/2MY2KP0
Read more

couldn't connect to server: EOF reached (code 1)

couldn't connect to server: EOF reached (code 1) I'm running a full node on my raspberry pi3. I try to do a simple command such as bitcoin-cli getblockchaininfo but I always get this error: error: couldn't connect to server: EOF reached (code 1) (make sure server is running and you are connecting to the correct RPC port) My bitcoin.conf file looks like this: Bitcoind options server=1 daemon=1 reindex-chainstate=1 reindex=1 txindex=1 disablewallet=1 listenonion=0 Connection settings rpcuser= * rpcpassword=* rpcport=8332 rpcallowip=127.0.0.1 rpcthreads=10 I also tried to get a command with "bitcoin-cli -rpcuser: * - rpcpassword=* -rpcportt8332 getblockchaininfo". But this also didn't work. Does someone has some advice or experience with this error? https://ift.tt/2D82TLW
Read more