Author

Topic: How best to store output descriptors/wallet backups (Read 162 times)

legendary
Activity: 2870
Merit: 7490
Crypto Swap Exchange
also regularly update the backups to include any changes or new addresses generated by the wallet.
That's not needed for HD-wallets. But you may want to backup your address labels once in a while.

Good point, label is important to ensure one's privacy. Although i don't recall output descriptor have field for label.
full member
Activity: 504
Merit: 144
I am wondering what the best practice is for storing output descriptors. Currently I have them offline on USB drives. However, there is an obvious risk of physical/environmental degradation over time. My instinct is that it would be foolish to save them on a cloud. I guess the tradeoff is physical degradation vs. being hacked. I'm guessing the latter is probably more likely.
USB drives are not the best because your USB drives more easily to have technical problems than with HDDs. Any drives can have technical problems and if you can not retrieve data in drives, you lose your backups.

Backup-wise practice will be making your backup in different drives, different formats like drives, paper, steel sheets. If one is damaged, you will have others to use and recover your wallet.

Security checklist
Securing your wallets
Bitcoin security and resources
5 common ways on how people lose their coins
Securing Your Seed Phrase with Washers fillippone.
legendary
Activity: 3290
Merit: 16489
Thick-Skinned Gang Leader and Golden Feather 2021
also regularly update the backups to include any changes or new addresses generated by the wallet.
That's not needed for HD-wallets. But you may want to backup your address labels once in a while.
jr. member
Activity: 35
Merit: 33
And you also can consider having multiple backup on different medium.
right, and also regularly update the backups to include any changes or new addresses generated by the wallet.  This ensures that your backup remains up-to-date.
legendary
Activity: 2534
Merit: 6080
Self-proclaimed Genius
I am wondering what the best practice is for storing output descriptors.
Those are quite long but you can write those on paper which you can store in a vault or something.
Just make sure to backup all descriptors for both internal and external chain, that makes 8 parent descriptors to backup (by default).

You can test if your backup can restore the correct keys by creating a blank wallet, import them all (importdescriptors)
and use the command: getaddressinfo "address" to see if it's "ismine" and "solvable" 'true'.
Use that command on your addresses of different script type, including the change.
Or you can also rely on the checksum which should be able to detect typos with relatively high reliability.
jr. member
Activity: 59
Merit: 31
Great ideas both of you, thanks!
legendary
Activity: 3290
Merit: 16489
Thick-Skinned Gang Leader and Golden Feather 2021
If you doubt your storage media, just create a new backup once in a while. Even $10 per year is enough to add a different brand stick to your collection annually.
legendary
Activity: 3374
Merit: 3095
Playbet.io - Crypto Casino and Sportsbook
Storing it offline is the best practice you should not connect to any device which is infected and connected online.  USB flash drives only have 10 years lifespan so holding backups on the USB flash drive is not for more than 10 years.

If you are looking for an alternative to store your backup for more than 10 years I think you can make a copy on DVD+RW according to Google it has a lifespan of more than 20-50 years and read-only CDs can live long more than 50 years. However, it still depends on how you take care of them.
jr. member
Activity: 59
Merit: 31
I am wondering what the best practice is for storing output descriptors. Currently I have them offline on USB drives. However, there is an obvious risk of physical/environmental degradation over time. My instinct is that it would be foolish to save them on a cloud. I guess the tradeoff is physical degradation vs. being hacked. I'm guessing the latter is probably more likely.
Jump to: