After reading this question 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?

2 Answers 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.


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)

  • 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 Feb 5, 2015 at 11:47
  • @NateEldredge You are right. It changed awhile ago it seems! I'll edit accordingly Feb 5, 2015 at 17:39
  • @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? Feb 9, 2015 at 4:49
  • Yes sure I tried it also for many wallets (test/main) Feb 9, 2015 at 9:27
  • @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). Feb 9, 2015 at 9:42

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

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