---
# System prepended metadata

title: Lightning Architectures / Breez

---

# Lightning Architectures / Breez

Episode will be framed as a casual conversation between us and `<project-rep>`. Our perspective is that we are curious about the different design tradeoffs projects make in service of good UX and broad adoption, while still maintaining a certain set of core principles.

## High-level questions

Questions about Breez's overall strategy, product direction and design decisions.

- Language Choices
    - Mobile Native vs. Flutter
    - LND vs c-lightning (go)
    - 

- Overall goals of Breez
    - Mobile UX guided by... e.g.:
        - is "full node on device" a priority?
        - are certain UX elements priorities

- Willing tradeoffs
    - What are the high-level tradeoffs Breez is willing to take to achieve above goals?
    - What are the things that Breez will never compromise in thinking through the design-space

- Working within contraints of a mobile environment
    - Always online
    - Creating a well enough connected channel
    - Mobile devices have intermittent connections


## Drilling into common UX problems

These will be questions that we see across different wallet implementations public key and from our own experience working in this design space.

**Privacy**
- Thinking about minimising UTXO privacy leaks
- Thinking through routing de-anonymisation
    - LSPs

**Backup/restore**
- What happens to funds if Breez disappears?
- How much technical knowledge (& prior personal infrastructure) does a user need to do backups (e.g. write down seed vs. photonJS ... channel state backups etc.)

**Custodial/non-custodial**
- Any temporary or permanent tradeoffs in service of UX e.g.:
    - Turbo channels
    - Submarine swaps
    - Who stores channel backups

**Spectrum of payment amounts**
- How do you handle *very small* transactions?
    - How do you do the initial onboard in a cost-effective way for a very small first transaction
- How do you handle *very large* transactions?
    - Wumbo channel and channel backups given "hot" context
        - Minimising trust (in Breez, & in LN) for larger amounts
    - Scaling of fees given that Lightning is proportional to amounts transferred and on-chain is fixed to byte-amount

## Technical questions

These questions will flow from the responses to the high-level questions above.

Examples would be like:
- Mobile performance questions
- Auxiliary services questions, how do they support UX goals (e.g. LNURL, submarine swaps)
- Auxiliary protocol elements to support UX goals (e.g. trampoline payments, watchtowers etc.)
- Unique concepts deployed (e.g. role of LSPs)
- Lightning at scale. Providing liquidity to onboard users a country like El Salvador.

## Future facing

***Provocation:** how does Lightning scale to the next 1 Billion users?*

- How does scaling work internally with current architecture?
- How does scaling work in the interactions between different players in LN ecosystem?
- Does a layered approach to scaling apply within Lightning itself (will there be layers to deploying Lightning)

## Potential open questions

- What are you most excited about in the space right now?
- What would you like to see improve in the space?
- What got you first excited about the space?
- Devil's advocate: what do you see as genuine threats to what folks are trying to do in the space? (where are our blind spots?)

