I consider you are complicated legacy addresses with legacy wallets. They’re distinct and unrelated issues.
- Legacy addresses are pre-segwit addresses (P2PKH mostly), and are contrasted with segwit and taproot addresses.
- Legacy wallets are pockets information within the BDB file format, created by outdated variations of Bitcoin Core (and might nonetheless be opened by new variations, for now). They’re contrasted with descriptor wallets, which use the SQLite file format, that are created by newer variations of Bitcoin Core.
You’ll be able to create legacy addresses utilizing descriptor wallets, and you may create segwit (however not taproot) addresses utilizing legacy wallets.
What I think is occurring right here is that you just’re attempting to carry out the dumpprivkey on a legacy deal with in a descriptor pockets. And that does not work, as a result of dumpprivkey solely works on legacy wallets (no matter deal with sort). Exporting non-public secret’s harmful, and particularly so for descriptor wallets (the place an attacker can sometimes compute all your non-public keys from only one). In the event you should, you possibly can export the non-public grasp key utilizing listdescriptors, although I think this is not going to be what you need.
That can assist you discover an alternate, I encourage you to amend your reply to elucidate precisely what you are attempting to realize (or level out if my interpretation of occasions is wrong). Maybe an answer exists that does not contain exporting non-public keys, as that’s usually a nasty concept until you actually know what you’re doing.