Inheritance Wallet Reference Design - Chapter 2 - Backup #1087
Conversation
- Text - Layout - Illustrations
Need to rewrite the content and create the prototype.
- Added image gallery for saving the backup. - Page structure changes - Naming changes
rabbitholiness
requested review from
danielnordh,
mouxdesign,
GBKS,
johnsBeharry and
sbddesign
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
|
|
||
| <div class="center" markdown="1"> | ||
|
|
||
| {% include image.html |
There was a problem hiding this comment.
This image does not seem to show up on my end.
|
|
||
| --- | ||
|
|
||
| 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. |
There was a problem hiding this comment.
| 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. | |
| 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. |
| 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. | |
| 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: | |
| 1. Private keys | |
| 2. Wallet configuration |
There was a problem hiding this comment.
Adds a good introductory sentence and fixes some awkward phrasing and sentence structure. Just a suggestion.
@mouxdesign this addresses your suggestion about a one-line mention of the use-case.
| 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. | |
| 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). |
|
|
||
| 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. |
There was a problem hiding this comment.
Idea to remind the reader of the use case here, could mention it as one sentence or link back to it.
|
|
||
| --- | ||
|
|
||
| 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. |
There was a problem hiding this comment.
Adds a good introductory sentence and fixes some awkward phrasing and sentence structure. Just a suggestion.
@mouxdesign this addresses your suggestion about a one-line mention of the use-case.
| 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. | |
| 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). |
| 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. |
There was a problem hiding this comment.
Removes repetition and improves phrasing.
| 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. | |
| The wallet configuration allows a recovery application 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 & spend the bitcoin. | |
| Thus, the Joneses need to safely backup and store six private keys as well as the wallet configuration. |
guide/inheritance-wallet/backup.md
Outdated
|
|
||
| ## Assembling the backup material | ||
|
|
||
| The illustration above reveals that Christina and David can access in two different ways. |
There was a problem hiding this comment.
I initially thought there was an illustration missing here, but it seems this sentence refers to the one on lines 99-108. I suggest this sentence can be moved to the previous section where it is closer to the illustration itself and also fits in context of the excellent advice you're providing there.
Co-authored-by: Mogashni <[email protected]>
Co-authored-by: yashrajd <[email protected]>
Co-authored-by: yashrajd <[email protected]>
Co-authored-by: yashrajd <[email protected]>
Co-authored-by: yashrajd <[email protected]>
Co-authored-by: yashrajd <[email protected]>
Co-authored-by: yashrajd <[email protected]>
Co-authored-by: yashrajd <[email protected]>
rabbitholiness
added
the
Inheritance wallet
This PR builds on Part 1 of the Family Inheritance Wallet reference design.
This page discusses how the backup process works and how the Joneses store and distribute different components of the backup material.
👁️ Check the preview here 👁️