Repository navigation
Inheritance wallet - Part 2 - Backup #1087
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
Changes from all commits
f64f5d5
0e59eb3
84c8132
cf3b206
ff585c2
4298959
7fc86b3
741c70e
cc1ebaa
fab4d78
01f4f15
0b72d75
55ed707
7506b52
284d944
bbb832f
2de3df4
2313e9b
95e43b5
84b1873
e687179
cb0289c
6c4f368
81f4864
7782609
5a57768
c696e33
5e4120b
82753dd
72dce66
5f3fc70
c255fd4
a2aeb65
6cf51fa
247a269
f17229a
fe7c7af
27470dc
92c0697
fecb65e
a556dd5
de3957d
93b9a50
4e7e071
f989731
79bf2e4
20011d0
2a4f207
bddcb8c
70ecfcc
215f987
5c584cc
46af3d2
ee95239
b11ccf3
0f303ba
2034e57
71e2a2e
2cfca5f
dacfa55
5b29ae5
f44e3dc
cfed02e
e752243
62b5b42
349cabc
b610ef2
d2eed39
06208a7
85326b5
9174903
a629a4d
81c54b3
97c6789
eefb1b2
dbedfc6
e00d842
331dd0c
18e3883
c0c1bc2
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -0,0 +1,173 @@ | ||||||
| --- | ||||||
| layout: guide | ||||||
| title: Wallet backup | ||||||
| description: This page gives an overview of how the Joneses backup their inheritance wallet. | ||||||
| nav_order: 3 | ||||||
| parent: Inheritance wallet | ||||||
| permalink: /guide/inheritance-wallet/backup/ | ||||||
| main_classes: -no-top-padding | ||||||
| image_base: /assets/images/guide/inheritance-wallet/ | ||||||
| images_wallet-backup: | ||||||
| - file: wallet-backup/app-home-backup-before | ||||||
| alt: Image of the app home screen showing a reminder to backup the wallet. | ||||||
| caption: The app shows a reminder to save the backup kit. | ||||||
| - file: wallet-backup/wallet-settings-backup-kit | ||||||
| alt: Screen showing instructions on how to store the wallet backup. | ||||||
| caption: The backup page highlights the most important points about the wallet backup and provides a link to learn more. | ||||||
| - file: wallet-backup/backup-save-dialog | ||||||
| alt: Placeholder screen representing the operating system native file download dialog. | ||||||
| caption: The file is saved using the native file download flow. | ||||||
| - file: wallet-backup/backup-success | ||||||
| alt: Screen showing a success message. | ||||||
| caption: The success screen reminds the user once again to not store the backup kit in the same place as the private key backups. | ||||||
| - file: wallet-backup/app-home-backup-done | ||||||
| alt: Image of the home screen that does not show the backup reminder anymore. | ||||||
| caption: The app home screen does not show the backup reminder anymore. | ||||||
| --- | ||||||
|
|
||||||
| <!-- | ||||||
|
|
||||||
| Editor's notes | ||||||
|
|
||||||
| This page covers how users backup their wallet and an example approach of how to store the backup material. | ||||||
|
|
||||||
| Illustration sources | ||||||
|
|
||||||
| https://www.figma.com/file/h5GP5v5dYfpXXfEUXf6nvC/Inheritance-wallet?type=design&node-id=6293%3A21917&mode=design&t=I2e3qgqYRGpAGyaQ-1 | ||||||
|
|
||||||
| --> | ||||||
|
|
||||||
| # Wallet backup | ||||||
| {: .no_toc } | ||||||
|
|
||||||
| --- | ||||||
|
|
||||||
| <div class="glossary-toc" markdown="1"> | ||||||
| * Table of contents | ||||||
| {:toc} | ||||||
| </div> | ||||||
|
|
||||||
| --- | ||||||
|
|
||||||
| The inheritance wallet described in this reference design is a multi-key wallet with time-based recovery. When backing up such a wallet, users must back up not only their own private keys but also the wallet configuration, as covered [here](https://bitcoin.design/guide/savings-wallet/time-based-recovery/#wallet-backup). | ||||||
|
|
||||||
| {% include picture.html | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The information definitely looks nicer as an image, but is also less accessible and super hard to read on mobile. You could. You could pull the text into the HTML or add a separate mobile image with a vertical layout. |
||||||
| image = "/assets/images/guide/inheritance-wallet/wallet-backup/multikey-backup-components.png" | ||||||
| retina = "/assets/images/guide/inheritance-wallet/wallet-backup/multikey-backup-components@2x.png" | ||||||
| alt-text = "A idagram showing the two parts of a multi-key wallet backup." | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
| width = 1600 | ||||||
| height = 800 | ||||||
| %} | ||||||
|
|
||||||
| The wallet configuration, also called [wallet descriptor](https://bitcoin.design/guide/glossary/#output-script-descriptor), gives a wallet application all the information it needs to generate addresses and identify the rules that define how bitcoin can be spent from these addresses. The private keys are required to sign transactions and spend the bitcoin. | ||||||
|
|
||||||
| Thus, the Joneses need to safely backup and store six private keys as well as the wallet configuration. | ||||||
|
|
||||||
| ### Private key backups | ||||||
| We have described best practices on how to back up private keys on the [bitcoin backups page](https://bitcoin.design/guide/how-it-works/backups/). | ||||||
|
|
||||||
| Our app emphasizes that users should keep one of the primary keys at all times, even if they move their funds to a new wallet. The reason is simple: there is still the possibility that some bitcoins will be sent to that old wallet. Keeping one of the keys around will make sure that users will be able to spend such funds, because the recovery path will be available to them. | ||||||
|
|
||||||
| ### Wallet configuration backup | ||||||
| The wallet configuration is backed up in the form of a collection of files packaged into a single backup kit. | ||||||
|
|
||||||
| #### Bob saves the backup kit | ||||||
| Once the wallet is created, the application prompts Bob to download the wallet backup kit. Bob saves the backup kit into his password manager that he has enabled on his phone. | ||||||
|
|
||||||
| {% include image-gallery.html pages = page.images_wallet-backup %} | ||||||
|
|
||||||
| Alice and Bob then encrypt the ZIP file with a strong password and both of them stores a copy of it in their personal password manager account, case they need to recover the wallet themselves. | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Question:
edit: realised this encrypted zip can be also shared with the lawyer. I have added it to my suggestion.
Suggested change
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah, I thought of that at as well, but then users would have to place more trust in the application. Don't know whether that would be a problem, though. |
||||||
|
|
||||||
| #### What is in the backup kit? | ||||||
| The backup kit is a ZIP folder that contains everything Bob and Alice might need to recover their wallet. Either because they replace their mobile phones or because they need to recover the wallet in a different wallet application: | ||||||
|
|
||||||
| <div class="center" markdown="1"> | ||||||
|
|
||||||
| {% include picture.html | ||||||
| image = "/assets/images/guide/inheritance-wallet/wallet-backup/backup-kit-contents.png" | ||||||
| retina = "/assets/images/guide/inheritance-wallet/wallet-backup/backup-kit-contents@2x.png" | ||||||
| alt-text = "An illustration showing what is included in the backup kit." | ||||||
| width = 450 | ||||||
| height = 450 | ||||||
| layout = "float-right-desktop" | ||||||
| %} | ||||||
|
|
||||||
| **A PDF file** that contains a QR code, the wallet descriptor and information about all six signing keys, including their XPUBs. Is also contains a visual representation of the rules that are used to unlock the recovery path and the inheritance key set. You can find an example of the recovery PDF at the bottom of this page. | ||||||
|
|
||||||
| **Wallet backup files in various formats** which can be used to import the wallet directly into other wallet applications like Bitcoin Core, Sparrow, Specter, Nunchuk or others. | ||||||
|
|
||||||
| </div> | ||||||
|
|
||||||
|
|
||||||
| ## Backup distribution | ||||||
|
|
||||||
| Alice and Bob are not willing to trust their life savings to one application. That's why they carefully chose the way in which they store the above wallet backup material. The illustration below shows the chosen setup in more detail. | ||||||
|
|
||||||
| {% include picture.html | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Make sure to add a mobile version with a vertical layout for easier reading. |
||||||
| image = "/assets/images/guide/inheritance-wallet/wallet-backup/recovery-tool-distribution.png" | ||||||
| retina = "/assets/images/guide/inheritance-wallet/wallet-backup/recovery-tool-distribution@2x.png" | ||||||
| modalImage = "/assets/images/guide/inheritance-wallet/wallet-backup/recovery-tool-distribution@2x.png" | ||||||
| alt-text = "A schematic illustration showing how the backup material is distributed between the parents, their children and the lawyer." | ||||||
| width = 1600 | ||||||
| height = 800 | ||||||
| modalWidth = 3324 | ||||||
| modalHeight = 1850 | ||||||
| %} | ||||||
|
|
||||||
| Please note that this is one of many possible ways to approach wallet backups and should not be understood as the only correct way to do it. | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. You could use tip formatting here. |
||||||
|
|
||||||
| It is important that users determine the best way to handle backups based on their own specific circumstances. Factors that will influence such decisions include the relationship between family members, the amount of funds stored, their access to safe locations, etc. Based on these and other factors it can be more appropriate to chose a simpler or more advanced backup scheme. | ||||||
|
|
||||||
| We would also like to reiterate the point made in the "Use case & scope" page: the complexity of the backup scheme increases with the complexity of the wallet configuration. Therefore, user education is critical during wallet creation as well as during the backup phase. | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Best to make that a link. |
||||||
|
|
||||||
| ## Accessing the backup material | ||||||
|
|
||||||
| Christina and David can access the multi-key wallet in two different ways. | ||||||
|
|
||||||
| #### Self-sovereign route | ||||||
| Bob and Alice want to provide the children a way to access the funds on their own, using only the backup parts that are stored in the house safe. They store the password in a tamper-evident bag, along with a USB drive. Since electronics can fail, they also place a printout of their will and the recovery PDF in it. | ||||||
|
|
||||||
| The PIN to the house safe is stored in the shared family vault in the password manager, where the family also keeps other digital items. | ||||||
|
|
||||||
| This is an acceptable trade-off for them, since they have good relationships and trust their children. After all, this is the reason they have chosen to include them in the setup in the first place. | ||||||
|
|
||||||
| Even if Christina and David breach that trust and recover the wallet, they would not be able to move the funds, because their inheritance keys are timelocked. They would only be able to see the balance and monitor transactions, but not spend any bitcoin. | ||||||
|
|
||||||
| Because Alice and Bob access their safe regularly, they would notice that the bag with the backup material has been opened. They can then safely move the funds to a new wallet, for which they would implement more restrictive security measures. | ||||||
|
|
||||||
| #### Assisted route | ||||||
|
|
||||||
| But what if the first route fails? In that case, Christina and David should have a way to gain access to the backup material by going through the standard legal procedures. This is why Bob and Alice give their lawyer Edward a copy of the encrypted backup kit. The password is stored in a deposit box at their bank, inside a tamper-evident bag. | ||||||
|
|
||||||
| This setup will prevent Edward from recovering the wallet, because he does not know how or where to access the backup kit password. It also prevents bank employees from doing so, because the backup kit is not stored in the deposit box along with the password. | ||||||
|
|
||||||
| But it will enable Christina and David to access both parts of the wallet backup through legal channels upon their parents' death. | ||||||
|
|
||||||
| #### Why backup redundancy? | ||||||
| The reason that there are two different ways in which Christina and David can gain access to the full backup material is redundancy. Redundancy is important because it is possible that one of the two routes fail. | ||||||
|
|
||||||
| ### Example resources | ||||||
|
|
||||||
| Below is an example of the backup PDF file. The first page contains the information about the wallet itself. This includes the name of the wallet as well as the [wallet descriptor](add link) in the form of a QR code as well as in clear text. It also shows a visual representation of the configuration of the key sets: | ||||||
|
|
||||||
| {% include picture.html | ||||||
| image = "/assets/images/guide/inheritance-wallet/wallet-backup/recovery-pdf.png" | ||||||
| retina = "/assets/images/guide/inheritance-wallet/wallet-backup/recovery-pdf@2x.png" | ||||||
| modalImage = "/assets/images/guide/inheritance-wallet/wallet-backup/recovery-pdf@2x.png" | ||||||
| alt-text = "An example of the recovery PDF file." | ||||||
| width = 1600 | ||||||
| height = 800 | ||||||
| modalWidth = 4050 | ||||||
| modalHeight = 2168 | ||||||
| %} | ||||||
|
|
||||||
| The subsequent pages describe the key sets and the individual signing keys, including the friendly names that Bob has given them. This will make it more convenient in case the wallet needs to be recovered. | ||||||
|
|
||||||
| --- | ||||||
|
|
||||||
| {% include next-previous.html | ||||||
| previousUrl = "/guide/inheritance-wallet/wallet-creation/" | ||||||
| previousName = "Wallet creation" | ||||||
| nextUrl = "/guide/upgradeable-wallet/" | ||||||
| nextName = "Upgradeable wallet" | ||||||
| %} | ||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Make sure to use relative links instead of absolute ones. Several instances of that on this page.