2

Based on the Developer Reference for importmulti, it seems the the timestamp property is purely used to determine how far back to rescan. If I have, say, 100 addresses and I simply set all of their timestamps to the same value (the earliest known timestamp), does this have any performance impact compared to setting each address' timestamp uniquely?

If the answer is no, then I'm wondering why this property was implemented as opposed to having a 3rd parameter holding a single "timestamp" for the entire list of addresses.

2

importmulti finds the earliest of the timestamps, and rescans from that point after all imports are done, yes. The wallet stores metadata about keys including the timestamp, which is why a timestamp is provided individually for each address rather than a single timestamp overall. Other commands like dumpwallet export a timestamp per key as well so this makes sense to provide it per-key when importing too, to save you having to look for the earliest before passing them in.

  • So, essentially the timestamp is used for ordering the list? – Max Vernon Nov 23 '17 at 3:48
  • @MaxVernon No need to order them, just start rescanning from the earliest, because in doing so you'll encounter all of them :) – MeshCollider Nov 23 '17 at 4:39
  • That makes sense. I can see how the timestamp can be a useful piece of info. Thanks for the answer. – dimsumcode Nov 23 '17 at 13:15

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.