You can already do this using importmulti, but importaddress, importprivkey and importpubkey are more easy to use if you are a human being using CLI, not a script.
Rationale is that I usually know creation date of my private keys when importing, for example, paper wallet. And full blockchain rescans are slow and unnecessary in such cases.
for importaddress, importprivkey and importpubkey
NACK, just create a client command to help with importmulti if that is the problem.
IMO this is not a strong reason to create redundancy on the RPC server. If this is accepted, clients can import multiple addresses by calling import* multiple times, which would incur in unnecessary rescans. importmulti is tweaked to scan only once for the given the batch.
Should have tests.
Yes, if decision is to not merge this, I will just create wrapper scripts for importmulti that will allow partial rescan for importing single privkey or address.
If this is accepted, clients can import multiple addresses by calling import* multiple times, which would incur in unnecessary rescans.
It is already possible with full rescans. This PR just adds option to do partial rescan instead.
Should have tests.
Will look at tests if this is accepted.
Ok, I didn’t know about that previous discussion. If it has been once discussed to not add this functionality, then no point to do that again.
Just some additional thoughts:
importaddress, importprivkey and importpubkey output some warnings they are deprecated in favour of importmulti?importmulti in addition to importing multiple keys?(that’s anyway different PR then, so I’m closing this)
Labels
RPC/REST/ZMQ