Related to my last question!

I wanted to know, is it possible to have an easily communicable process for users to dump out private keys for taproot addresses in Bitcoin Core? It turns out the answer is ... no! (unless you can contradict me - I'd be very happy!)

Whilst it's easy to generate taproot addresses in the new-brand "descriptor wallets" (bitcoin-cli getnewaddress address_type=bech32m), and you can inspect the descriptors for the wallet with bitcoin-cli listdescriptors and even inspect the master private key with bitcoin-cli listdescriptors true, you *cannot* do what used to be easy with bitcoin-cli dumpprivkey address. Now there's a simple logic behind not exposing raw private keys - they lack context. I've seen sipa explain this to people in a few places, it makes sense. A privkey really needs the context of what address it should attach to (even though possible address types can be iterated, that's not a great counter argument, etc, sidetrack.) So, we have descriptors and we can use them to deal with that. The raw privkey (and pubkey) information will still be inside them. But there's more - see achow's answer to the question here: https://bitcoin.stackexchange.com/a/107956

This is an additional step of restriction - it was actively decided not to allow private key export for individual addresses, because of the issue, well known for over a decade by developers in the field, that *individual* private keys of unhardened branches expose *all* private keys in that branch. They're very dangerous in that sense, and it isn't reasonable to expect an every day user to know that.

It's arguable, but I think this decision is dubious at best. A person running the kinds of commands I'm mentioning above is not exactly a normal user; if bitcoin core's wallet is anything, it's a power user wallet, and last and most importantly, dangerous things can be gated behind warnings. A thing should only be *prevented* if there is literally no use case, and I don't think people reading their own private keys quite qualifies there. (And i speak as a wallet dev who has told people countless times "never read your private key!" as a security heuristic..)

A reminder, it used to be literally one-line `bitcoin-cli dumpprivkey