Sure, importprivkey will cease being supported fully each time 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 personal keys, utilizing the importdescriptors RPC, which has totally different arguments and totally 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 rationale for not supporting importprivkey in legacy wallets is that its conduct is tough to cause about, and deliberately not supported anymore for descriptor wallets:
importprivkeyis successfully a “here’s a key, work out what I need to do with it”. It can trigger sure (however not all) single-key addresses associated to that key to turn into a part of the pockets, however it’s 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 on the whole), you must be specific about what/the way you need to use the important thing.
