importmulti
inside the help for importprivkey
seems useful.
importprivkey
is redundant and ideally could be deprecated.
Really? Huh, okay. I don’t think that’s widely known.
Edit: keeping as is, since there are apparently cases where importmulti
can’t be used yet.
Yes, I think importmulti
is superior in every way, except:
The latter can be fixed by just adding support for that case. The former can be improved by adding ‘default’ cases (e.g. if you prove a WIF private key, it can permit omitting the address, …).
99@@ -100,6 +100,7 @@ UniValue importprivkey(const JSONRPCRequest& request)
100 throw std::runtime_error(
101 "importprivkey \"privkey\" ( \"label\" ) ( rescan )\n"
102 "\nAdds a private key (as returned by dumpprivkey) to your wallet. Requires a new wallet backup.\n"
103+ "\nHint: use importmulti to import more than one private key!\n"
Style nits. Feel free to ignore:
Adds a private key...
and Hint: use...
!
. .
will do!I agree that @sipa’s two points here: #12702 (comment) should be addressed, but I don’t see any harm in adding this hint until those are done.
ACK 8fb733756bc6119958a9807d83bde1a4a99cac31 with a couple of style nits.