# Design review call #8

_January 18, [Issue](https://github.com/BitcoinDesign/Meta/issues/49)_
22 people
Started an hour earlier

---

## BTCPay via Pavlenex

Intro to the project via slides from a conference in Riga in 2019. See [here](https://www.slideshare.net/AndrewCamilleri11/btcpayday-2019-riga-introduction-to-btcpay-server).

Looking for some design help related to the following:
- Onboarding, setting up a wallet
- Thoughts on integrating a setup wizard
- Identifying and brainstorming solutions to users pain points
- Unifying bitcoin and lightning
- Coin selection

Design process:
- Process is about quickly getting features to users and then cleaning them up later
- No designer for 2 years
- Now a dedicated one
- Issues labelled design on Github
- Design meetings
- Mock-ups on Figma

## Hexa Wallet via Anant

- [Slides](https://docsend.com/view/8w6tnr3sq24amt2z)
- Differentiate between backup scheme and transaction keys. One is used to see and sign transactions, the other is to restore the wallet as a whole
- The backup scheme takes the mnemonic and shares it amoung keepers
- Mnemonic seeds score well on resistance to loss and resistance to theft (better than other techniques)
- Multisig has benefits, but also complications,,
- Using Shamir Secret Sharing to split mnemonic into 5 parts which are shared across multiple devices (which may belong to other people)
- Redesign of backup
- Red shield too scary, options too complex for new users with low amounts
- Moving to progressive security based on 3 levels
- Level 1 - single key
- Level 2 - add 2 keepers
- Level 3 - add 2 more keepers
- Regular reminder to re-enter security info
- Home screen keeps users informed
- Positive feedback on user flow, minor feedback on language

## Zeus Wallet via Evan

- [Site](https://zeusln.app/)
- Started as passion project, wallet to connect to own Lightning node
- React Native
- 10+ languages, contribute via Transifex
- Supports various Lightning node standards
- Various integrations with BTCPay, Umbrel, etc
- Target audience of full node operators, various features for channel management but main use case is for spending on the go
- Goal of encouraging full node use, get newcomers onboarded into the system
- Educate users, let them start simple and allow them to level up when they are ready for it
- Feedback to simplify onboarding flow, fewer options per screen, make UI elements more consistent, bake in "good defaults"
- Overall happy with the feature set, UI needs improvement
- Open to design contributors, check the site for Github and other links