Sure, importprivkey will cease being supported fully at any time when help for legacy wallets is eliminated, in all probability in model 28.0. Previous wallets will after all be covertible to the brand new format.
Nonetheless, it’s completely potential to import issues into new wallets that contain non-public keys, utilizing the importdescriptors RPC, which has completely different arguments and completely different semantics, however nearly actually covers your use case. See the documentation for importprivkey, which mentions:
Word: This command is barely appropriate with legacy wallets. Use “importdescriptors” with “combo(X)” for descriptor wallets.
The explanation for not supporting importprivkey in legacy wallets is that its conduct is difficult to motive about, and deliberately not supported anymore for descriptor wallets:
importprivkeyis successfully a “here’s a key, work out what I wish to do with it”. It’s going to trigger sure (however not all) single-key addresses associated to that key to develop into a part of the pockets, however it is going to additionally do issues like making a multisig script the pockets knew about go from watch-only to totally supported if it now has all its keys.- With
importdescriptor(and the philosophy behind descriptor wallets typically), you need to be express about what/the way you wish to use the important thing.
