Skip to content
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

Inheritance Wallet Reference Design - Chapter 2 - Backup #1087

Open
wants to merge 78 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from 67 commits
Commits
Show all changes
78 commits
Select commit Hold shift + click to select a range
f64f5d5
Initial structure
rabbitholiness Feb 27, 2024
0e59eb3
Section structure
rabbitholiness Feb 27, 2024
84c8132
changed file locations and paths
rabbitholiness Feb 28, 2024
cf3b206
Landing page text
rabbitholiness Feb 28, 2024
ff585c2
Add introduction page
rabbitholiness Mar 1, 2024
4298959
Added content to sub-pages
rabbitholiness Mar 1, 2024
7fc86b3
Added content to backups page
rabbitholiness Mar 1, 2024
741c70e
Distributed initial text to sub-pages
rabbitholiness Mar 1, 2024
cc1ebaa
Finalized landing page text
rabbitholiness Mar 13, 2024
fab4d78
Introduction page text updates
rabbitholiness Mar 13, 2024
01f4f15
Text updates
rabbitholiness Mar 13, 2024
0b72d75
Illustration test
rabbitholiness Mar 14, 2024
55ed707
Added illustrations to the introduction page
rabbitholiness Mar 14, 2024
7506b52
Updated illustration
rabbitholiness Mar 14, 2024
284d944
Text updates to the wallet creation page
rabbitholiness Mar 14, 2024
bbb832f
Landing page updates
rabbitholiness Mar 15, 2024
2de3df4
Update for illustrations
rabbitholiness Mar 18, 2024
2313e9b
Updated illustration avatars and reshuffled content
rabbitholiness Mar 18, 2024
95e43b5
added mobile illustrations
rabbitholiness Mar 18, 2024
84b1873
Final touches on the text
rabbitholiness Mar 19, 2024
e687179
First draft wallet creation page copy
rabbitholiness Mar 19, 2024
cb0289c
Removed items from later releases
rabbitholiness Mar 26, 2024
6c4f368
Text changes
rabbitholiness Mar 26, 2024
81f4864
Smaller text updates
rabbitholiness Mar 26, 2024
7782609
Updated navigation links
rabbitholiness Mar 26, 2024
5a57768
Added onboarding screens
rabbitholiness Mar 26, 2024
c696e33
Fixed problem with image gallery
rabbitholiness Mar 26, 2024
5e4120b
Added image placehodlers
rabbitholiness Mar 26, 2024
82753dd
Added all image galleries
rabbitholiness Apr 9, 2024
72dce66
Finalized copy and page structure
rabbitholiness Apr 9, 2024
5f3fc70
Text updates
rabbitholiness Apr 9, 2024
c255fd4
Added the prototype, needs more tweaking
rabbitholiness Apr 12, 2024
a2aeb65
Update guide/inheritance-wallet/landing-page.md
rabbitholiness Apr 15, 2024
6cf51fa
Update guide/inheritance-wallet/landing-page.md
rabbitholiness Apr 15, 2024
247a269
Update guide/inheritance-wallet/introduction.md
rabbitholiness Apr 15, 2024
f17229a
Update guide/inheritance-wallet/wallet-creation.md
rabbitholiness Apr 15, 2024
fe7c7af
Update guide/inheritance-wallet/wallet-creation.md
rabbitholiness Apr 15, 2024
27470dc
Update guide/inheritance-wallet/wallet-creation.md
rabbitholiness Apr 15, 2024
92c0697
Update guide/inheritance-wallet/wallet-creation.md
rabbitholiness Apr 16, 2024
fecb65e
Update guide/inheritance-wallet/wallet-creation.md
rabbitholiness Apr 22, 2024
a556dd5
Update guide/inheritance-wallet/introduction.md
rabbitholiness Apr 22, 2024
de3957d
Integrating feedback
rabbitholiness Apr 22, 2024
93b9a50
Update guide/inheritance-wallet/landing-page.md
rabbitholiness Apr 22, 2024
4e7e071
Text update
rabbitholiness Apr 22, 2024
f989731
Added image captions
rabbitholiness Apr 22, 2024
79bf2e4
Structural updates
rabbitholiness Apr 23, 2024
20011d0
Wallet creation updates
rabbitholiness Apr 25, 2024
2a4f207
Minor structural updates
rabbitholiness Apr 25, 2024
bddcb8c
Inheritance key updates
rabbitholiness Apr 25, 2024
70ecfcc
Minor text updates
rabbitholiness Apr 25, 2024
215f987
Added image captions
rabbitholiness Apr 25, 2024
5c584cc
Added remaining alt texts
rabbitholiness Apr 26, 2024
46af3d2
Removed obsolete images
rabbitholiness Apr 26, 2024
ee95239
Updated design consideration section
rabbitholiness Apr 26, 2024
b11ccf3
Updated prototype
rabbitholiness Apr 29, 2024
0f303ba
Initial commit
rabbitholiness May 2, 2024
2034e57
Image updates
rabbitholiness May 3, 2024
71e2a2e
Image and link fixes
rabbitholiness May 3, 2024
2cfca5f
Minor tweaks
rabbitholiness May 3, 2024
dacfa55
Updated links from/to other pages
rabbitholiness May 3, 2024
5b29ae5
Broken links & text fixes
rabbitholiness May 3, 2024
f44e3dc
Multiple tweaks
rabbitholiness May 3, 2024
cfed02e
small text change
rabbitholiness May 3, 2024
e752243
Navigation item renaming
rabbitholiness May 3, 2024
62b5b42
Added modal images
rabbitholiness May 6, 2024
349cabc
Added captions and alt texts
rabbitholiness May 6, 2024
b610ef2
Tweaked modal images
rabbitholiness May 6, 2024
d2eed39
Update guide/inheritance-wallet/backup.md
rabbitholiness May 14, 2024
06208a7
Update guide/inheritance-wallet/backup.md
rabbitholiness May 14, 2024
85326b5
Update guide/inheritance-wallet/backup.md
rabbitholiness May 14, 2024
9174903
Update guide/inheritance-wallet/backup.md
rabbitholiness May 14, 2024
a629a4d
Update guide/inheritance-wallet/backup.md
rabbitholiness May 14, 2024
81c54b3
Update guide/inheritance-wallet/backup.md
rabbitholiness May 14, 2024
97c6789
Update guide/inheritance-wallet/backup.md
rabbitholiness May 14, 2024
eefb1b2
Update guide/inheritance-wallet/backup.md
rabbitholiness May 14, 2024
dbedfc6
Update guide/inheritance-wallet/backup.md
rabbitholiness May 29, 2024
e00d842
Addressing Yashraj's feedback
rabbitholiness May 29, 2024
331dd0c
Addressing Mo's feedback
rabbitholiness May 29, 2024
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
Binary file added assets/images/guide/inheritance-wallet/header.jpg
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might make more sense here to create an example of one wallet, for understanding the context of the image more. one wallet name then showing many different file types. The image used does make sense as it seems you are trying to convey that different wallets can use different file types but the relatedness of those file types is confusing visually. If that relatedness could be grouped or shown, might make more sense.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated and made a more concrete example. Hope it's clearer now.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the diagram the word wallet descriptor is used, however in the copy wallet configuration is used in the opening paragraph and the copy below the image. Might be good to choose one term and use to it both with image and copy.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wallet descriptor copy in image:
"A small piece of text", further below in the copy it seems that the small piece of text is the backup kit. Might be worth changing the copy in the image to keep it consistent.

If I understand correctly the backup kit is exportable as a ZIP file.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion to image copy:
Heading: Wallet configuration.
Body copy: A pdf file as well as wallet backup files in various contexts that a wallet would need to recover a multi-key wallet.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated and rephrased. Hope it makes more sense now.

166 changes: 166 additions & 0 deletions guide/inheritance-wallet/backup.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,166 @@
---
layout: guide
title: Wallet backup
description: This page gives an overview of how the Joneses backup their savings wallet.
rabbitholiness marked this conversation as resolved.
Show resolved Hide resolved
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>

---

As we have covered in the time-based recovery [reference design](https://bitcoin.design/guide/savings-wallet/time-based-recovery/#wallet-backup) there are two parts to backing up a multi-key wallet: the private keys as well as the wallet configuration.
rabbitholiness marked this conversation as resolved.
Show resolved Hide resolved

{% include picture.html
image = "/assets/images/guide/inheritance-wallet/wallet-backup/multikey-backup-components.png"
retina = "/assets/images/guide/inheritance-wallet/wallet-backup/[email protected]"
alt-text = "An illustration showing the two parts of a multi-key wallet backup."
width = 1600
height = 800
%}

Users need not only to back up the individual private keys that are used to sign transactions. But they also have to back up the wallet configuration as such. This is needed for recovery, because the wallet application needs to know how to generate addresses and the rules that define how bitcoin can be spent from these addresses.

This means that, in our use case, the Joneses need to safely backup and store six private keys as well as the wallet configuration.
rabbitholiness marked this conversation as resolved.
Show resolved Hide resolved
rabbitholiness marked this conversation as resolved.
Show resolved Hide resolved

### Private key backups
Of course, all six private keys need to be backed up properly. We describe some best practices on how to back up private keys on the [bitcoin backups page](https://bitcoin.design/guide/how-it-works/backups/), so we won’t be covering this topic here.
rabbitholiness marked this conversation as resolved.
Show resolved Hide resolved

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
After the wallet has been created, the application prompts Bob to download the wallet backup kit.
rabbitholiness marked this conversation as resolved.
Show resolved Hide resolved

#### Bob saves the backup kit
Bob saves the the backup kit into his password manager that he has enabled on his phone.
rabbitholiness marked this conversation as resolved.
Show resolved Hide resolved

{% 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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question:

  • can you explain how encrypting the zip file helps Alice & Bob with recovering the wallet?
    My understanding is that this step keeps the backup kit safe from evil cloud providers or password manager...

edit: realised this encrypted zip can be also shared with the lawyer. I have added it to my suggestion.

  • could the earlier step of saving to pw manager on phone be skipped, instead opting for this?
    Suggestion: the application itself could generate a pw-protected zip file so the users don't have to do it.
Suggested change
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.
Alice and Bob then encrypt the ZIP file with a strong password and store a copy in their personal password manager accounts. This encrypted file can also be shared with their lawyer for assisted recovery.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The 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 just a ZIP file that contains the following contents:
rabbitholiness marked this conversation as resolved.
Show resolved Hide resolved

- **A PDF file** that contains the wallet descriptor and information about all six XPUBs. Is also contains a visual representation of the rules that are used to unlock the recovery path and the inheritance key set.
- **Wallet backup files in various formats**, which can be used to import the wallet to other wallet applications like Sparrow, Nunchuk or others.

{% include picture.html
image = "/assets/images/guide/inheritance-wallet/wallet-backup/backup-kit-contents.png"
retina = "/assets/images/guide/inheritance-wallet/wallet-backup/[email protected]"
alt-text = "An illustration showing what is included in the backup kit."
width = 1600
height = 800
%}

## 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
image = "/assets/images/guide/inheritance-wallet/wallet-backup/recovery-tool-distribution.png"
retina = "/assets/images/guide/inheritance-wallet/wallet-backup/[email protected]"
modalImage = "/assets/images/guide/inheritance-wallet/wallet-backup/[email protected]"
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.

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.

## Assembling the backup material

The illustration above reveals that Christina and David can access in two different ways.
rabbitholiness marked this conversation as resolved.
Show resolved Hide resolved
rabbitholiness marked this conversation as resolved.
Show resolved Hide resolved

#### 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.

But even if Christina and David would 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 they would not be able to spend any bitcoins.
rabbitholiness marked this conversation as resolved.
Show resolved Hide resolved

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, in a tamper-evident bag.
rabbitholiness marked this conversation as resolved.
Show resolved Hide resolved

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/[email protected]"
modalImage = "/assets/images/guide/inheritance-wallet/wallet-backup/[email protected]"
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"
%}
167 changes: 167 additions & 0 deletions guide/inheritance-wallet/landing-page.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,167 @@
---
layout: guide
title: Inheritance wallet
description: An in-depth UX reference design for a multi-key bitcoin wallet with inheritance features designed for families.
nav_order: 6
has_children: true
permalink: /guide/inheritance-wallet/
main_classes: -no-top-padding
image: https://bitcoin.design/assets/images/guide/inheritance-wallet/header.png
image_base: /assets/images/guide/inheritance-wallet/
images_creation-wallet-basics:
- file:
alt:
caption:


---

<!--

Editor's notes

This page covers ....

Illustration sources

https://www.figma.com/file/h5GP5v5dYfpXXfEUXf6nvC/Family-inheritance-wallet?type=design&node-id=5542%3A2119&mode=design&t=sBtcvrDzb8MPtWaK-1

-->

{% include picture.html
image = "/assets/images/guide/inheritance-wallet/header.jpg"
alt-text = "An image showing two parents handing bitcoin to their two children."
width = 1600
height = 600
layout = "full-width"
%}

# Family inheritance wallet
{: .no_toc }

The family inheritance wallet is an app designed to create flexible wallets for family savings. It offers features designed to help with sustainable long-term storage and inheritance planning.

But when it comes to inheritance, technology is not everything. Knowledge, documentation, practice and social processes are important for any setup to work over the long term. This exploration includes not only designs and prototypes of the wallet application, but also thoughts around social processes to ensure that funds will not be lost.

## What are we building?

Imagine a product that helps you create and use a custody setup for your bitcoin savings while including your loved ones from the beginning. But because you plan to live a long and happy life, the app allows you to set up a recovery path that helps you recover your funds even in catastrophic scenarios.

On top of that, the app allows you to add your heirs' hardware wallets and use them to create a dedicated inheritance key set. Since it is designed for long-term storage, it also includes regular key checks and other supporting features.

All of this is done without compromising your financial privacy. You don't want anyone to know how much bitcoin you have or monitor your transactions.

## Chapters

### [Use case & scope]({{ '/guide/inheritance-wallet/introduction/' | relative_url }})

<div class="center" markdown="1">

{% include image.html
image = "assets/images/guide/inheritance-wallet/icon-introduction.png"
retina = "assets/images/guide/inheritance-wallet/[email protected]"
alt-text = ""
width = 80
height = 80
layout = "float-left"
link-url = "/guide/inheritance-wallet/introduction/"
%}

Before we dive into the details, we will introduce you to the Jones family. We are also going to look at how they plan set up their family savings in general.

</div>

---

### [Wallet creation]({{ '/guide/inheritance-wallet/wallet-creation/' | relative_url }})

<div class="center" markdown="1">

{% include image.html
image = "assets/images/guide/inheritance-wallet/icon-wallet-creation.png"
retina = "assets/images/guide/inheritance-wallet/[email protected]"
alt-text = ""
width = 80
height = 80
layout = "float-left"
link-url = "/guide/inheritance-wallet/wallet-creation/"
%}

Our application lets users create flexible multi-key wallets with timelocked recovery paths to help them recover funds while they are still alive. On top of that, users can create and manage dedicated inheritance keys that are held by their heirs.

</div>

---

### [Wallet backup]({{ '/guide/inheritance-wallet/backup/' | relative_url }})

<div class="center" markdown="1">

{% include image.html
rabbitholiness marked this conversation as resolved.
Show resolved Hide resolved
image = "assets/images/guide/inheritance-wallet/icon-wallet-backup.png"
retina = "assets/images/guide/inheritance-wallet/[email protected]"
alt-text = ""
width = 80
height = 80
layout = "float-left"
link-url = "/guide/inheritance-wallet/backup/"
%}

When backing up multi-key wallets there are more moving parts to consider than with single-key wallets. Our application helps users with that.

</div>

---

### Operational phase (coming soon)

<div class="center" markdown="1">

{% include image.html
image = "assets/images/guide/inheritance-wallet/icon-operations.png"
retina = "assets/images/guide/inheritance-wallet/[email protected]"
alt-text = ""
width = 80
height = 80
layout = "float-left"
link-url = "/guide/inheritance-wallet/regular-use/"
%}

Over time it might become necessary for users to make changes to their savings wallet because someone lost a key or they want to make changes to the overall wallet configuration. Our app helps users to make such changes and update the backup and inheritance documentation. It also helps with regular key checks.

</div>

---

### Recovery & inheritance (coming soon)

<div class="center" markdown="1">

{% include image.html
image = "assets/images/guide/inheritance-wallet/icon-recovery.png"
retina = "assets/images/guide/inheritance-wallet/[email protected]"
alt-text = ""
width = 80
height = 80
layout = "float-left"
link-url = "/guide/inheritance-wallet/wallet-recovery/"
%}

When it's time for the heirs to claim their inheritance, the Jones' children can use their own signing devices to recover their funds.

</div>

---

**Resources**
- [Figma design file](https://www.figma.com/file/h5GP5v5dYfpXXfEUXf6nvC/Family-inheritance-wallet?type=design&node-id=5542%3A2119&mode=design&t=sBtcvrDzb8MPtWaK-1)
- [Custom spending conditions]({{ '/guide/how-it-works/custom-spending-conditions/' | relative_url }})

---

{% include next-previous.html
previousUrl = "/guide/savings-wallet/time-based-recovery/"
previousName = "Time-based recovery"
nextUrl = "/guide/inheritance-wallet/introduction/"
nextName = "Use case & scope"
%}