Backing up wallet.dat | Bitcointalksearch.org

Maged

legendary

Activity: 1204

Merit: 1015

Quote from: TheMagikarp on June 01, 2011, 07:46:05 AM

So if I were to make 3 transactions a day, every day, I'd need to update my backup roughly every month, with no backup much older than that having all my Bitcoins in it.

Please correct me if I'm wrong.

That's correct, assuming that you are re-using your receiving addresses instead of manually generating a new one.

vuce

sr. member

Activity: 476

Merit: 250

Quote from: Pieter Wuille on June 01, 2011, 06:24:46 AM

The key pool was introduced in 0.3.14

Restoring of a wallet backup is supported since 0.3.20 with -rescan, in earlier versions you had to remove the block database and redownload it.

Since 0.3.21, -rescan is done automatically.

this is weird then, I'm running 0.3.21beta

TheMagikarp

newbie

Activity: 26

Merit: 0

So if I were to make 3 transactions a day, every day, I'd need to update my backup roughly every month, with no backup much older than that having all my Bitcoins in it.

Please correct me if I'm wrong.

Pieter Wuille

legendary

Activity: 1072

Merit: 1181

The key pool was introduced in 0.3.14

Restoring of a wallet backup is supported since 0.3.20 with -rescan, in earlier versions you had to remove the block database and redownload it.

Since 0.3.21, -rescan is done automatically.

vuce

sr. member

Activity: 476

Merit: 250

Quote from: Pieter Wuille on June 01, 2011, 05:44:21 AM

The only actions that require fresh keys from the pool, are change sent back when sending a payment, and generations (mining). You can do at least 100 such actions before a new backup is required.

yesterday I tried restoring a wallet from backup and lost what was sent back with the previous transaction (shows as debit to the newly created address, which obviously isn't in the wallet). There was only one transaction difference between the two wallets. When was this "100 key pool by default" introduced?

Pieter Wuille

legendary

Activity: 1072

Merit: 1181

The only actions that require fresh keys from the pool, are change sent back when sending a payment, and generations (mining). You can do at least 100 such actions before a new backup is required.

foo

sr. member

Activity: 409

Merit: 250

Quote from the Wiki: https://en.bitcoin.it/wiki/Securing_your_wallet

Quote

The wallet contains a pool of queued keys. By default there are 100 keys in the key pool. The size of the pool is configurable using the "-keypool" command line argument. When you need an address for whatever reason (send, “new address”, generation, etc.), the key is not actually generated freshly, but taken from this pool. A brand new address is generated to fill the pool back to 100. So when a backup is first created, it has all of your old keys plus 100 unused keys. After sending a transaction, it has 99 unused keys. After a total of 100 new-key actions, you will start using keys that are not in your backup. Since the backup does not have the private keys necessary for authorizing spends of these coins, restoring from the old backup will cause you to lose Bitcoins.

TheMagikarp

newbie

Activity: 26

Merit: 0

I've created a backup of my wallet.dat (in a TrueCrypt container, of course) and have it stored in 7 or 8 different places.

I read somewhere that if you go too long without updating your wallet.dat that it can become out of date and won't work properly anymore, something to do with only 99 receiving addresses being stored in the file. Realistically, how often should I update my backups to make sure they stay functioning? I intended on updating them roughly once a month. Is this not often enough, or is it more often than I really need to worry about?

I receive 1-2 payments a day, on average, if that makes any difference.

Topic: Backing up wallet.dat (Read 2742 times)