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

Family inheritance wallet reference design - Part 1 #1081

Open
wants to merge 55 commits into
base: master
Choose a base branch
from

Conversation

rabbitholiness
Copy link
Collaborator

@rabbitholiness rabbitholiness commented Mar 18, 2024

This multi-page reference design looks at a multi-key wallet for family savings. It includes a recovery path as well as a timelocked inheritance key set. Apart from wallet creation, the reference design also addresses topics like wallet backups, key rotation and recovery.

This PR addresses the first part of the series, which will cover the landing page, the use case description and the wallet creation flow. The outline of the entire reference design is described on the landing page and marked as "coming soon". The remaining pages will be added step by step.

👉 Preview it here 👈

@rabbitholiness rabbitholiness self-assigned this Mar 18, 2024
Copy link

netlify bot commented Mar 18, 2024

Deploy Preview for bitcoin-design-site ready!

Name Link
🔨 Latest commit b11ccf3
🔍 Latest deploy log https://app.netlify.com/sites/bitcoin-design-site/deploys/662f62c59887430008428cf3
😎 Deploy Preview https://deploy-preview-1081--bitcoin-design-site.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@mouxdesign
Copy link
Collaborator

Just reviewed the wallet creation page, looks great, really like how vibrant and friendly the designs look.

Some ideas:
The user flow itself is split into 3 distinct sections, each of those having subsections under each. As a builder landing on this page the flow is pretty detailed. To manage the expectations of the builder, if they commit to building this out in their wallet then how much of complexity would it require. See that there is a high level menu at the top which allows the reader to navigate however that would be more to navigate the content. A higher level overview could help with this in the beginning, this can be an image or text setting expectations:

Step1: First configure wallet

  1. Primary keyset (add keys)
  2. Create recovery path
  3. Create dedicated inheritance keyset
    Are any of these steps optional?

Step 2: Add signing keys

  1. Primary
  2. Inheritance keys

Step 3: Finalize the wallet

Spelling:
there was one small typo on one of the screen designs:
Screenshot 2024-04-22 135736
Custom "answer a couple of questions"

Other than that the language on the page is nice and easy to understand, you did a really great job of that considering how complex this topic is.

@rabbitholiness
Copy link
Collaborator Author

Just pushed a quite extensive update. Here's the TL;DR:

Use case & scope page:

  • Clarified and elaborated on the role that the wallet provider plays as well as the approach taken in this reference design, based on @GBKS feedback.
  • Structured the second half of the page into a "Design considerations" section.

Wallet creation page:

  • Added more structure to the page content, based on @mouxdesign feedback.
  • Updated designs and image galleries for adding signing keys. They now reflect the non-custodial approach of the application. The original designs are still available in Figma.
  • Added captions and missing alt texts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Inheritance wallet Referring to the inheritance wallet reference design.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants