<p>It is usually longer than 2 minutes...
<br>Please look at the blockchain as a database storing addresses and balances.<br>
If you have an address (privkey) from the very beginning, you search in the blockchain for records about your address.<br>
But if you import address, which was unknown to this client, you have to go through blockchain once again, in order to search for records corresponding to this address. Elsewhere, how could you know balance of this address, if you didn't look at it before importing?<br>
In my opinion, it doesn't prevent you from importing anything. <br>If you want to skip rescan, use <code>bitcoind importprivkey l12n3lj2nl2n3213lkj4n3lk4n false</code>. You can import a lot of privkeys this way, and rescan at the end with the last address or via start switch <code>bitcoind -rescan</code>.<br>
Please note that rescaning is not necessary when importing keys with 0 BTC.</p>

CC BY-SA 3.0
2013-08-15T18:45:57.083Z
If you are correct ("it doesn't prevent you from importing anything") then the Bitcoin Wiki should be corrected.
RentFree
CC BY-SA 3.0
2013-08-15T23:49:30.880Z
Yeah sounds like the reason is not correct according to this answer. Although if you click over to the wiki, there is an optional new_key parameter. It's ambiguous as to whether the author meant it was checking to see of the new key was already used, which makes more sense.
Neil Neyman
CC BY-SA 3.0
2013-08-16T08:30:06.187Z
@NeilNeyman You are absolutely right. I suppose it was written by a non-native English speaker, because such context in many European languages means what I mentioned in my post.
ripazha
CC BY-SA 3.0
2013-08-15T17:36:06.077Z
2013-08-15T17:36:06.077Z
ripazha
<p>According the <a href="https://en.bitcoin.it/wiki/How_to_import_private_keys" rel="nofollow">the Bitcoin Wiki</a>, when importing a private key:</p>

<blockquote>
  <p>Bitcoind will rescan the entire
  block data <strong>to ensure this key has not been used before</strong>.
  This process will take from one to two minutes,
  depending on your CPU performance. DO NOT abort it before finishing!</p>
</blockquote>

<p>Why is this scanning necessary?  Wouldn't this prevent me from changing from one bitcoin client to another, because that would involve importing (used) private keys from the old client into the new?</p>

<private-key>
Why can't I import a used private key?
RentFree
# Why can't I import a used private key?

(Asked by: username_0 on 2013-08-15)

According the [the Bitcoin Wiki](https://en.bitcoin.it/wiki/How_to_import_private_keys), when importing a private key:

> Bitcoind will rescan the entire
> block data **to ensure this key has not been used before**.
> This process will take from one to two minutes,
> depending on your CPU performance. DO NOT abort it before finishing!

Why is this scanning necessary? Wouldn't this prevent me from changing from one bitcoin client to another, because that would involve importing (used) private keys from the old client into the new?

**Tags:** private-key


---

## 1 answers

### Answer by username_1 on 2013-08-15. Score: 3 | Accepted answer

It is usually longer than 2 minutes...
  
Please look at the blockchain as a database storing addresses and balances.  
If you have an address (privkey) from the very beginning, you search in the blockchain for records about your address.  
But if you import address, which was unknown to this client, you have to go through blockchain once again, in order to search for records corresponding to this address. Elsewhere, how could you know balance of this address, if you didn't look at it before importing?  
In my opinion, it doesn't prevent you from importing anything.   
If you want to skip rescan, use `bitcoind importprivkey l12n3lj2nl2n3213lkj4n3lk4n false`. You can import a lot of privkeys this way, and rescan at the end with the last address or via start switch `bitcoind -rescan`.  
Please note that rescaning is not necessary when importing keys with 0 BTC.

> **Comments:**
> **username_0**: If you are correct ("it doesn't prevent you from importing anything") then the Bitcoin Wiki should be corrected.  
> **username_2**: Yeah sounds like the reason is not correct according to this answer. Although if you click over to the wiki, there is an optional new_key parameter. It's ambiguous as to whether the author meant it was checking to see of the new key was already used, which makes more sense.  
> **username_1**: @username_2 You are absolutely right. I suppose it was written by a non-native English speaker, because such context in many European languages means what I mentioned in my post.  

---

