Repository navigation
Inheritance wallet - Part 3 - Cosigner onboarding & key replacement - #1091
rabbitholiness wants to merge 79 commits into
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
✅ Deploy Preview for bitcoin-design-site ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
Opened this PR in draft mode so far, so that people can look at it. There's quite a few things to tweak:
|
Also some main copy tweaks and mockup updates.
|
Opening this up for initial feedback, even if there are two things left to do:
|
mouxdesign
left a comment
There was a problem hiding this comment.
LGTM, some comments on the use of specific names of hardware wallets. I would recommend avoiding those so that the copy remains timeless and not brand specific.
| So far, the wallet has been created on Bob's app. The next step is to get Alice set up as a cosigner and to enable her to sign transactions. To do this Alice needs to: | ||
|
|
||
| 1. Import the wallet configuration to her app. | ||
| 2. Enable her Bitbox to sign transactions. |
There was a problem hiding this comment.
| 2. Enable her Bitbox to sign transactions. | |
| 2. Enable her hardware wallet to sign transactions. |
There was a problem hiding this comment.
I see your point. However, I would probably keep the device names. I know they're brands, but I think it's easier for the reader to follow along, if they are specific examples. In addition, these brands have been around for a long time, so I wouldn't be too worried about that.
There was a problem hiding this comment.
How about we make up our own brands - BitGuard, CoinSafe, and BlockVault? I've done this before with mock-ups and it usually works well.
Co-authored-by: Mogashni <90313394+mouxdesign@users.noreply.github.com>
Co-authored-by: Mogashni <90313394+mouxdesign@users.noreply.github.com>
GBKS
left a comment
There was a problem hiding this comment.
Looking good. Just some minor feedback.
|
|
||
| --- | ||
|
|
||
| So far, the wallet has been created on Bob's app. The next step is to get Alice set up as a cosigner and to enable her to sign transactions. To do this Alice needs to: |
There was a problem hiding this comment.
So far could link back to the point you are referring to. Users can of course figure it out themselves, but you might as well save them that small effort.
|
|
||
| Editor's notes | ||
|
|
||
| This page covers a multi-key wallet that uses timelocks to provide additional recovery options. |
| images_alice-enable-device: | ||
| - file: alice-enable-device/enable-alice-home | ||
| alt: Home screen showing the wallet with two tasks associated. | ||
| caption: Alice is ready to enable her Bitbox to sign transactions for the wallet. |
There was a problem hiding this comment.
| caption: Alice is ready to enable her Bitbox to sign transactions for the wallet. | |
| caption: Alice is ready to enable her BitBox to sign transactions for the wallet. |
The second B is also capitalized. Make sure to update that across your PRs.
|
|
||
| ### Replacing a signing key | ||
|
|
||
| Let's assume that David has lost his signing device. He did not lose the seed phrase backup, so he could theoretically just import his private key into a new device. But since they are dealing with their family savings, the Joneses don't want to take any chances. They decide to replace David's key, which is part of the inheritance key set, with a new one. They would follow the same approach if David had lost the seed phrase backup or had reason to believe that it had been compromised. |
There was a problem hiding this comment.
They would follow the same approach if David had lost the seed phrase backup
Why is that? Can't he just recreate it from his signing device? Is it because someone might find the lost backup?
| 2. Activate the new wallet on their signing devices. | ||
| 3. Save the backup kit for the new wallet. | ||
|
|
||
| We have covered these topics in the previous pages of this reference design. |
|
|
||
| #### Alice co-signs the transaction | ||
|
|
||
| On the app home screen, Alice now sees a reminder that a transaction is ready to be signed. On the detail screen, she also sees that Bob has already provided a signature. Alice hits "sign" and goes through the transaction signing flow on her Bitbox. |
There was a problem hiding this comment.
now sees a reminder that a transaction is ready to be signed
How does the app know about the transaction? Is there a server handling communication? If not, then Bob would have to share the PSBT.
|
|
||
| After she has signed the transaction, she sees that the transaction is being confirmed by the network. Once the transaction has been confirmed, the app home screen shows a reminder that the original wallet should be archived. | ||
|
|
||
| ### Archiving the old wallet |
There was a problem hiding this comment.
Could cross-link to the archival paragraph in the multi-wallet page somewhere.
|
I will open a new PR, as I had technical issues with the existing branch. |

This PR builds on the previous inheritance wallet PRs:
Part 1: Use case & wallet creation
Part 2: Wallet backup
It adds a page about how Alice is set up as a cosigner for the family savings wallet. It also adds a page about how making changes work, like key replacement or editing timelocks.