usually you just need to see if your wallet size is increase, if it is true then you need a new backup, otherwise not
keypool size is about 100 btw(so after it reach you need a new back up you don't need to do it after every new address)
Topic: Automating bitcoind wallet backup based upon keypool size & usage (Read 1863 times)
April 10, 2015, 12:08:02 AM
This seems rather important.
Can't the dump tell you how many keys are in the pool?
Will a restore of a dump(if using dumpwallet) populate the keypool, my experiments seem to suggest that the keypool will be rebuilt as if empty(if the new wallet is created with keypool=0)?
dumpwallet is chosen over backupwallet because it looks simpler to interrogate.
Can't the dump tell you how many keys are in the pool?
Will a restore of a dump(if using dumpwallet) populate the keypool, my experiments seem to suggest that the keypool will be rebuilt as if empty(if the new wallet is created with keypool=0)?
dumpwallet is chosen over backupwallet because it looks simpler to interrogate.
March 24, 2013, 07:27:56 PM
IMO no
March 24, 2013, 07:22:17 PM
It's my understanding that in order to ensure that your wallet backups will contain all your transactions, you should at a minimum back up your wallet every new addresses that you generate. Are there any best practices for how to achieve this other than keeping counters on your own that are triggered by your application logic at the same time you ask bitcoind for a new address?
Jump to: