Hot answers tagged

3

Change in this case represent external/internal chain. Usually if that's external chain, you can share it with parties. Imagine having a client which is obliged to send you bitcoin very often. If you'd give him xpub for the whole external chain, he can generate addresses on his own and you don't have to be bothered. It's not heavily used, but sometimes ...


2

You are on the right track. The address is derived correctly, it is just not encoded with the right version. You need to add the testnet network version to the btc.payments.p2pkh call as well. Something like this should work: console.log(btc.payments.p2pkh({pubkey, network: btc.networks.testnet}).address); The address should then start with m... instead ...


2

No, Bitcoin Core uses the BIP32 derivation path m/0'/0', and you are unable to change the derivation path of the wallet in Bitcoin Core. There is however the Hardware Wallet Interface (HWI) that might be what you are looking for. https://github.com/bitcoin-core/HWI https://github.com/bitcoin-core/HWI/blob/master/docs/bitcoin-core-usage.md


1

You seem to have confused a couple of things. Firstly, HD wallets is specified by BIP 32, not BIPs 39 or 44. Secondly, being able to set your own seed is completely unrelated to setting a custom derivation path. They are two different things that have no effect on each other. Note that BIP 39 specifies a menmonic scheme, not a seed. When I say mnemonic, I ...


1

If the above two keys are leaked, then your master private key at the account level (m/44'/60'/4') can be back-calculated. That means, any private key (both receiving and change) that you derive from that account is compromised. To elaborate, BIP 44 uses non-hardened derivation to derive private keys after the account level. The child private key derivation ...


Only top voted, non community-wiki answers of a minimum length are eligible