New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bitcoin-QT grandfather - father - son wallet backup built in? #2692
Comments
Backups on the same hard drive/location aren't really proper backups... |
It could give a reminder when a new backup is needed either based on the number of keypool keys generated or "keypoololdest", that was my idea with #2637. Maybe a "backup status" on the overview page that shows this info... |
I'd like to invest into this direction. What if the client would have a periodical or event-based backup routine? Backups could be only allowed if the client has a encrypted wallet. Backups should be possible to internal storage (with warning) and/or external storage. Internal storage could be "wallet.dat.backup20150101" in the same directory or backups to user defined URIs on the "local" filesystem. Now to earn some critics: i would love the possibility to make a backup of my [encrypted!] wallet to my dropbox / google drive or other "external space". bitcoind/Bitcoin-QT should give a nice interface to the available backups. For hardcore bitcoind users it's might be needless. But for simple endusers it could be a life-saver. |
Closing. Now that all newly created wallets are HD, I think a feature like this is no longer required. |
Having recently suffered a fairly minor loss due to wallet corruption, and being a little lax with backups (hence the only minor loss), I was wondering if anyone would be inspired to build a simple backup system into the QT client, i.e. whenever a spend transaction is made and a new change address is generated, a copy of the wallet.dat is made named for example wallet.dat.backup, and a copy of any pre-existing wallet.dat.backup is renamed as wallet.dat.old deleting any previous wallet.dat.old file. I know some people may see this as 'your fault, you should back up properly', but in the real world how many people do this every single time a new keypair is made?
The text was updated successfully, but these errors were encountered: