Quote from: nc50lc on Today at 04:08:06 AM

The reason for the same xprv key is because it's your wallet's "master private key" which is the 'm' in the derivation path which is at the upper most level of the hierarchy.
The different xpubs on the other hand, are derived down to the account level (see its position in the descriptor) which are derived with different derivation paths as seen in your 8 descriptors.

They implement the different address types? (I see: pkh, sh(wpkh), tr and wpkh). When I switch to BIP 44 (in IanColeman's BIP39 tool), I get legacy addresses. Exactly the legacy addresses that getnewaddress outputs with:

Code:

bitcoin-cli -rpcwallet=MyWallet getnewaddress -address_type legacy

And as Account Extended Public Key the xpubkey of the corresponding descriptor is displayed. I think I'm starting to understand this. I don't understand the math but what it does.

Quote from: nc50lc on Today at 04:08:06 AM

Example descriptors:

Yes, that's what they look like. When you talk about "change", do you mean the Bitcoins , which are transferred to yourself if you do not spend the total amount in the inputs? This is the path with the "1" (m/84'/0'/0'/1) I think.
If I set "External / Internal" to "1" in the BIP39 tool, the path changes and other addresses are generated. These are then the internal addresses for the change?

Quote from: nc50lc on Today at 04:08:06 AM

Quote from: tiffy

Can I then also create unsigned transactions with the watch-only wallet, which I then sign on my cold wallet?

In Bitcoin Core, it can be done with RPC commands.
Or in the GUI, you'll just need to activate "Enable PSBT controls" in the wallet settings.

You have helped me a lot again.