Lexe call 1

Whats Lexe about?

• They are building a bitcoin and LN wallet
• Main difference is architecture like breeze, they run it in a hardware enclave (cannot extract the private keys of the users)
• Solves offline recieve problem, this is because they have a node online all the the time.

Goal: trying to build the best possible UX

UX Challenges:

• Struggle with how to bring back the standard to a self custodial LN wallet, contacts and how to make that work?

• Being self custodial, users are in theory supposed to audit the node code and approve an upgrade (there should be a flow for that)

  In order for clients to trust it, making sure that that is seamless, leaning towards an auto update

• How do you get people to write a mental model with inbound and outbound liquidity?

  • Inbound liquidity, lost of wallets operate like this they create an invoice and receive a payment. The LSP will intersect the payment (Just in time channel) and then they provide free liquidity to the user. Most users dont have a notion of a max receive amount. How do we communicate this to the user without confusing them?

  GUIDE:

  • bitcoin design guide: receiving bitcoin page
  • Usage lifecycle framework

• Dev question: “Should we allow users to optimize the fees?”

Where are they in the build process?

Who do you want to build this product for?

Q: What resources/screens design guide did you sue when you first started out? Why did you use these? Why did you find it useful?

• Downloaded every wallet and then borrowing from every wallet.