I'm not sure as to why the keypool is still being used
To make it easier to implement HD into Core with minimal review. There are plans to generate HD keys on the fly instead of storing them in a keypool. 
Topic: What is key pool used for? (Read 180 times)
The key pool is generated from your master key. In the past, the non-HD client maintain 100 private keys in the wallet file for the user to use, by default. This allows the user to use that file to backup the wallet file and restore the addresses for 100 transactions; Bitcoin uses a new address for every transaction.
I'm not sure as to why the keypool is still being used. The addresses in it is being generated with the master key. The 2000 keys that is generated is the same as the 2000 key in the keypool. They are used when your wallet needs a new address. The number is maintained whenever your wallet is unlocked.
I'm not sure as to why the keypool is still being used. The addresses in it is being generated with the master key. The 2000 keys that is generated is the same as the 2000 key in the keypool. They are used when your wallet needs a new address. The number is maintained whenever your wallet is unlocked.
In the wallet file, upon the node's first start up, a HD master key is generated and 2000 keys are created, but dumping the wallet file shows there are also 2000 key pools saved in the wallet file too, what are they used for? It looks a key pool is just a public key plus an additional time variable?
Jump to: