<p>The value <code>1392447127 is exactly Sat, 15 Feb 2014 06:52:07 GMT</code> in  Unix timestamp 
check it here : <a href="http://www.onlineconversion.com/unix_time.htm" rel="nofollow">http://www.onlineconversion.com/unix_time.htm</a></p>

<p><code>keypoololdest</code> gives the unix timestamp of the oldest key in the key pool (which stores unused keys). This timestamp can be used to check if a wallet backup still covers all your used keys or a new one needs to be created.</p>

<p>At the latest, if the timestamp retrieved with <code>keypoololdest</code> gives a date younger than your youngest backup, you should create a new backup.</p>

CC BY-SA 3.0
2016-10-13T16:42:18.480Z
2016-10-13T18:01:37.983Z
2016-10-13T18:01:37.983Z
Badr Bellaj
<p>The keypool, as the name suggests, is a pool of keys stored in your wallet.dat file for various functions including:</p>

<ul>
<li>change addresses</li>
<li>new addresses</li>
</ul>

<p>By default you'll have 100 keys. Each time you use a key for change or receiving, there'll be one less key in the pool. A new key is added to replenish the used key.</p>

<p>The oldest key (from February 2014) represents the age of the oldest key. In other words, you're storing BTC at an address that was created in February 2014. Replenishing the keypool doesn't update the date because that would mean the private key for the oldest (and still useful!) key has been cleared. </p>

<p>There's no inherent issue, per se, with old keys, if they're secured. </p>

<p>(Although encrypting your wallet will replenish all keys since a compromised wallet would reveal a sizeable portion if the now encrypted keypool) </p>

CC BY-SA 3.0
2015-02-05T11:47:37.810Z
but I didn't understand why it didn't change to be today's date instead of this tiny change (from 1392447127 to 1392449568), and also they recommend to take a backup if the keypoololdest is greater than your last backup ! for that I'm asking
Mohamed Farrag
CC BY-SA 3.0
2015-02-05T17:39:52.390Z
@NateEldredge You are right. It changed awhile ago it seems! I'll edit accordingly
Wizard Of Ozzie
CC BY-SA 3.0
2015-02-09T04:49:13.870Z
@MohamedFarrag have you got BTC in an address which is from the wallet.dat private keys? Is your computer system time correct? Is your blockchain synced?
Wizard Of Ozzie
CC BY-SA 3.0
2015-02-09T09:27:17.363Z
Yes sure I tried it also for many wallets (test/main)
Mohamed Farrag
CC BY-SA 3.0
2015-02-09T09:42:25.463Z
@MohamedFarrag What about the first part? Is there BTC associated with a key in your wallet.dat that's been there a long time? Best way to check is by enabling advanced options (I'm on iOS so I can't remember the exact options), then click SEND, in the top field there'll be an expansion for inputs which will be the addresses with UTXOs (unspent outputs).
Wizard Of Ozzie
CC BY-SA 3.0
2015-02-05T09:40:17.657Z
2015-02-05T17:44:55.667Z
2015-02-05T17:44:55.667Z
Wizard Of Ozzie
<p>After reading this <a href="https://bitcoin.stackexchange.com/questions/35572/how-many-addresses-does-my-wallet-dat-contain-do-i-need-to-make-a-new-backup-ev">question</a> I watched the <code>keypoololdest</code>. </p>

<ul>
<li>It was 1392447127 (Sat, 15 Feb 2014 06:52:07 GMT)</li>
<li>I created a new address.</li>
<li>Then, it was 1392449568 (Sat, 15 Feb 2014 07:32:48 GMT)</li>
</ul>

<p>Should the time change to be today at the moment of change? It is too old (like one year ago) . If I took a backup now is it sufficient until the "keypoololdest" changes to be more recent than the date of the backup?</p>

<bitcoin-core><keypool>
What does the keypoololdest field mean?
Mohamed Farrag
# What does the keypoololdest field mean?

(Asked by: username_0 on 2015-02-05)

After reading this [question](https://bitcoin.stackexchange.com/questions/35572/how-many-addresses-does-my-wallet-dat-contain-do-i-need-to-make-a-new-backup-ev) I watched the `keypoololdest`.

* It was 1392447127 (Sat, 15 Feb 2014 06:52:07 GMT)
* I created a new address.
* Then, it was 1392449568 (Sat, 15 Feb 2014 07:32:48 GMT)

Should the time change to be today at the moment of change? It is too old (like one year ago) . If I took a backup now is it sufficient until the "keypoololdest" changes to be more recent than the date of the backup?

**Tags:** bitcoin-core, keypool


---

## 2 answers

### Answer by username_1 on 2016-10-13. Score: 2

The value `1392447127 is exactly Sat, 15 Feb 2014 06:52:07 GMT` in Unix timestamp
check it here : <http://www.onlineconversion.com/unix_time.htm>

`keypoololdest` gives the unix timestamp of the oldest key in the key pool (which stores unused keys). This timestamp can be used to check if a wallet backup still covers all your used keys or a new one needs to be created.

At the latest, if the timestamp retrieved with `keypoololdest` gives a date younger than your youngest backup, you should create a new backup.


---

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

The keypool, as the name suggests, is a pool of keys stored in your wallet.dat file for various functions including:

* change addresses
* new addresses

By default you'll have 100 keys. Each time you use a key for change or receiving, there'll be one less key in the pool. A new key is added to replenish the used key.

The oldest key (from February 2014) represents the age of the oldest key. In other words, you're storing BTC at an address that was created in February 2014. Replenishing the keypool doesn't update the date because that would mean the private key for the oldest (and still useful!) key has been cleared.

There's no inherent issue, per se, with old keys, if they're secured.

(Although encrypting your wallet will replenish all keys since a compromised wallet would reveal a sizeable portion if the now encrypted keypool)

> **Comments:**
> **username_0**: but I didn't understand why it didn't change to be today's date instead of this tiny change (from 1392447127 to 1392449568), and also they recommend to take a backup if the keypoololdest is greater than your last backup ! for that I'm asking  
> **username_2**: @NateEldredge You are right. It changed awhile ago it seems! I'll edit accordingly  
> **username_2**: @username_0 have you got BTC in an address which is from the wallet.dat private keys? Is your computer system time correct? Is your blockchain synced?  
> **username_0**: Yes sure I tried it also for many wallets (test/main)  
> **username_2**: @username_0 What about the first part? Is there BTC associated with a key in your wallet.dat that's been there a long time? Best way to check is by enabling advanced options (I'm on iOS so I can't remember the exact options), then click SEND, in the top field there'll be an expansion for inputs which will be the addresses with UTXOs (unspent outputs).  

---

