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 – Mohamed Farrag – 2015-02-05T11:47:37.810
@NateEldredge You are right. It changed awhile ago it seems! I'll edit accordingly – Wizard Of Ozzie – 2015-02-05T17:39:52.390
@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 – 2015-02-09T04:49:13.870
Yes sure I tried it also for many wallets (test/main) – Mohamed Farrag – 2015-02-09T09:27:17.363
@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 – 2015-02-09T09:42:25.463