<p>Clicking "generate new address" takes a time, because after returning one fresh address form the pregenerated pool, an actual new one is generated to refill the pool with.</p>

CC BY-SA 3.0
2012-01-28T10:06:07.593Z
True, lol, I should have realised that!
o0'.
CC BY-SA 3.0
2012-01-27T23:43:42.827Z
2012-01-27T23:43:42.827Z
Pieter Wuille
<blockquote>
  <p>This would be cool, but how do I check it is really true?</p>
</blockquote>

<p>I haven't tried this:</p>

<p>Backup your wallet.dat and generate a new receiving address.  Then delete wallet.dat and restore from the backup.  Now generate a "new" receiving address.  It should be the same one as the first one.</p>

<p>Convinced?</p>

CC BY-SA 3.0
2013-05-02T07:39:54.407Z
2013-05-02T07:39:54.407Z
Eyal
<p>you can check by directly exploring the content of your wallet.dat file, which is a bdb database. there are various tools for exploring the wallet, one of which is gavin's bitcointools: <a href="https://github.com/gavinandresen/bitcointools" rel="nofollow">https://github.com/gavinandresen/bitcointools</a></p>

<p>Another exporter is <a href="https://github.com/jackjack-jj/pywallet" rel="nofollow">pywallet.py</a>.</p>

CC BY-SA 3.0
2012-01-19T18:36:06.660Z
2012-01-27T23:04:17.287Z
2012-01-27T23:04:17.287Z
nanotube
<p>I'm using the standard commandline client (under OSX, in case this matters).</p>

<p>I've read in some threads that it is smart enough to pregenerate 100+ addresses to be used in future when you ask them, so that if you backup an earlier wallet, the future private keys are not lost.</p>

<p>This would be cool, but how do I check it is really true?</p>

<p>Every time I "get a new address", it seemed to me it took enough time to suspect it was generating it on the fly, not using it from a pregenerated pool. Maybe it was slow for other reasons, though, and that's why I'd like to check somehow.</p>

<bitcoin-core><address>
How do I know my wallet.dat actually already contains 100+ addresses ready to be used?
o0'.
# How do I know my wallet.dat actually already contains 100+ addresses ready to be used?

(Asked by: username_0 on 2012-01-19)

I'm using the standard commandline client (under OSX, in case this matters).

I've read in some threads that it is smart enough to pregenerate 100+ addresses to be used in future when you ask them, so that if you backup an earlier wallet, the future private keys are not lost.

This would be cool, but how do I check it is really true?

Every time I "get a new address", it seemed to me it took enough time to suspect it was generating it on the fly, not using it from a pregenerated pool. Maybe it was slow for other reasons, though, and that's why I'd like to check somehow.

**Tags:** bitcoin-core, address


---

## 3 answers

### Answer by username_3 on 2012-01-19. Score: 5 | Accepted answer

you can check by directly exploring the content of your wallet.dat file, which is a bdb database. there are various tools for exploring the wallet, one of which is gavin's bitcointools: <https://github.com/gavinandresen/bitcointools>

Another exporter is [pywallet.py](https://github.com/jackjack-jj/pywallet).


---

### Answer by username_1 on 2012-01-27. Score: 3

Clicking "generate new address" takes a time, because after returning one fresh address form the pregenerated pool, an actual new one is generated to refill the pool with.

> **Comments:**
> **username_0**: True, lol, I should have realised that!  

---

### Answer by username_2 on 2013-05-02. Score: -1

> This would be cool, but how do I check it is really true?

I haven't tried this:

Backup your wallet.dat and generate a new receiving address. Then delete wallet.dat and restore from the backup. Now generate a "new" receiving address. It should be the same one as the first one.

Convinced?


---

