2
I have a need to generate a new extended public key (xpub).
Examples:
xpub6CUGRUonZSQ4TWtTMmzXdrXDtypWKiKrhko4egpiMZbpiaQL2jkwSB1icqYh2cfDfVxdx4df189oLKnC5fSwqPfgyP3hooxujYzAu3fDVmz
tpubD6NzVbkrYhZ4WLczPJWReQycCJdd6YVWXubbVUFnJ5KgU5MDQrD998ZJLNGbhd2pq7ZtDiPYTfJ7iBenLVQpYgSQqPjUsQeJXH8VQ8xA67D
How can I do this?
I would like to do it inside json rpc, because that would help automate testing, but I ultimately don't care how I get them. They are for testing.
0
You can generate new extended public keys on
You can generate them for testnet or mainnet. Just set the network combo box in the upper right to the network you want.
ADVISO: Please don't ever use websites to generate key material. Suitable only for throw-away addresses for testing only.
1
You can do that, but each HD seed needs to be inside its own wallet file which is loaded by the server. Running bitcoind with multiple -wallet arguments will achieve what you are aiming for. Currently it is not supported to dynamically load and unload wallets at runtime, but support for that is being added and will be available in a future release.
Exporting xpub from bitcoin node doesn't server purpose as it uses hardened key derviation... you need to export the xprv https://bitcoin.stackexchange.com/questions/50244/how-to-get-xpub-or-mpkbip32-for-my-bitcoin-core-wallet?noredirect=1&lq=1
– dark knight – 2018-04-23T08:48:38.047@toddmo you can generate a valid xpub any way you like if you just want one for testing, it doesn't have to be the same one as the one in your wallet – MeshCollider – 2018-04-24T02:11:31.660
ok I put a lot of effort into editing my question and doing research, which provided an answer, which may not be the best. Sorry but I needed to learn what I needed to ask and cut out all the extraneous babbling in my original question. Now you can see what I really want by looking at my edited question and my new answer. Again, sorry. Feel free to give a better answer than mine. – toddmo – 2018-04-24T03:04:40.600