<p><code>importmulti</code> 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 <code>dumpwallet</code> 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.</p>

CC BY-SA 3.0
2017-11-23T03:48:43.983Z
So, essentially the timestamp is used for ordering the list?
Hannah Vernon
CC BY-SA 3.0
2017-11-23T04:39:16.277Z
@MaxVernon No need to order them, just start rescanning from the earliest, because in doing so you'll encounter all of them :)
meshcollider
CC BY-SA 3.0
2017-11-23T13:15:44.183Z
That makes sense. I can see how the timestamp can be a useful piece of info.  Thanks for the answer.
dimsumcode
CC BY-SA 3.0
2017-11-23T02:02:41.477Z
2017-11-23T02:02:41.477Z
meshcollider
<p>Based on the <a href="https://bitcoin.org/en/developer-reference#importmulti" rel="nofollow noreferrer">Developer Reference</a> for <code>importmulti</code>, it seems the the <code>timestamp</code> 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?</p>

<p>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.</p>

<timestamp><import>
Are there performance implications using the "timestamp" property of ImportMulti in the following way?
dimsumcode
# Are there performance implications using the "timestamp" property of ImportMulti in the following way?

(Asked by: username_0 on 2017-11-23)

Based on the [Developer Reference](https://bitcoin.org/en/developer-reference#importmulti) 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.

**Tags:** timestamp, import


---

## 1 answers

### Answer by username_1 on 2017-11-23. Score: 2 | Accepted answer

`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.

> **Comments:**
> **username_2**: So, essentially the timestamp is used for ordering the list?  
> **username_1**: @MaxVernon No need to order them, just start rescanning from the earliest, because in doing so you'll encounter all of them :)  
> **username_0**: That makes sense. I can see how the timestamp can be a useful piece of info.  Thanks for the answer.  

---

