generate segwit addresses?

I would like to see both P2SH (3...) and bech32 (bc1...) segwit addresses alongside each regular P2PHK (1...) address, since those are generated by Bitcoin Core since the most recent release.

[dooglus]

When I created this issue I wasn’t aware that you had already added tabs for segwit addresses.

Bitcoin Core’s HD wallet implementation appears to use a single index for all 3 types of addresses it supports. So the first 100 addresses (m/0’/0’/0’ through m/0’/0’/99’) in my wallet are ‘legacy’ P2PHK addresses, then the next 20 (m/0’/0’/100’ through m/0’/0’/119’) are P2SH wrapped segwit addresses, and from there on they’re all bech32 addresses, except for when I come across a site that won’t accept a bech32 address to withdraw to, in which case I use a P2SH address.

So when I generate a bech32 receiving address in Bitcoin Core, but the site I give it to rejects it, I would like to be able to quickly find the corresponding 1… or 3… address to give to the site instead. I can do this by switching tabs, but then I have to somehow figure out what the yprv or zprv extended private key is (Bitcoin Core only tells you the xprv key), and wait for it to regenerate the addresses.

Maybe if it automatically switched the xprv for the corresponding yprv or zprv when I switch tabs and/or script semantics it would be less frustrating. I’m entering the xprv in the “BIP32 Root Key” field, which blanks the mnemonic field, but the value I enter isn’t changed when I switch tabs, and I see an error “Invalid root key”. I think that all that would need doing would be to replace the first 4 bytes of the base58-decoded xprv with the magic bytes for yprv or zprv keys as required.

[Querzel]

Perhaps my issue regarding LTC xprv -> BIP49 & BIP84 is relevant here ? https://github.com/iancoleman/bip39/issues/96#issuecomment-501747295