Skip to content

Add ⚡️ Lightning services page to Designing Bitcoin products chapter #532

Closed

Description

@Bosch-0

The wallets we are focused on modelling the guide's content around (Phoenix, Breez, Muun etc.) all have great UX due to offering various 'Lightning services.' These entities that provide these are what you call 'Lightning service providers' or LSPs. I am proposing we include a page in the DBP chapter about these Lightning services and how LSPs can use them. Everything should be detailed within a design context of course.

As we add Lightning content to the various sections of the guide it will be almost impossible to illustrate great UX flows without mentioning Lightning services. This page should do the heavy lifting on the details of these services and should be referenced to from the more practical sections of the guide (onboarding, payments etc.) similar to the Technology primer.

Below is a rough outline of sections that would be in this page. All of these are pretty much interoperable except probably the warm node / backup and recovery.

  • Payment forwarding (warm node - node doesn't have to be online 24/7).
    • Potential custodial issues with this?
  • Inbound liquidity
  • Turbo channels
  • Backup and recovery
  • Route calculation
    • Trampoline nodes
  • Swaps (on-chain <-> Lightning)
  • Watchtowers
  • Lightning address for easy payments
  • Meta LN services like LN+, Amboss, Lighting Terminal. These aren't really end user services but may be worth noting them at the bottom of the page.

Activity

  1. johnsBeharry commented on Oct 19, 2021

    @johnsBeharry
    Contributor

    Concept ACK. It also is a good idea to model it after the tech primer.

    Inbound liquidity*

    • This may be one of the most common LSP types as it may be the first (and only) connections to lightning someone has.

    Lighting Terminal

    • haven't used but from what I gather is more of a management dashboard, its on the application layer instead of service layer.

    Amboss, LN+

    • These two can be seen as "LSP Directories", especially LN+.
    • So I'd argue they are end user services as they are solving a discovery problem of channel partners + liquidity.
    • A bitcoin application can aggregate and filter from multiple directories and filter them based on some questionnaire that captures their preferences.
    • Might have some link to the software overview page though as Amboss especially in its current state at least seems similar to an explorer.
  2. pavlenex commented on Oct 19, 2021

    @pavlenex
    Contributor

    As we dive deep into wallets, it will become obvious that LSP is something that will be a part of development process and an important decision for the product makers. It can also be monetizaiton way as well as a way to improve the UX. However it comes with a lots of risks, so it'll be interesting to see if yields of being an LSP are good enough to offset the risk people have when being a LSP. Decisions such as choosing an LSP or being an LSP for your users can also be taken into consideration.

    Concept ack and agreed with both of you, especially like the structure Johns pointed out.

  3. kingonly commented on Oct 22, 2021

    @kingonly

    Suggest to use zero-conf channels instead of turbo channels. We don't need an extra marketing layer to describe the tech.

  4. changed the title [-]Add `Lightning service providers` page to `Designing Bitcoin products` chapter[/-] [+]Add `Lightning services` page to `Designing Bitcoin products` chapter[/+] on Oct 27, 2021
  5. self-assigned this
    on Oct 28, 2021
  6. added this to the Milestone #10 milestone on Nov 2, 2021
  7. changed the title [-]Add `Lightning services` page to `Designing Bitcoin products` chapter[/-] [+]Add ⚡️ `services` page to `Designing Bitcoin products` chapter[/+] on Nov 7, 2021
  8. pavlenex commented on Nov 15, 2021

    @pavlenex
    Contributor

    @Bosch-0 is this something we'd still want to tackle in the Milestone #10 or should we postpone it for later revision?

  9. Bosch-0 commented on Nov 16, 2021

    @Bosch-0
    CollaboratorAuthor

    @pavlenex How's about we include it in the next milestone so we can wrap up 10 :)

  10. moved this from Todo 📝 to In Progress 🏗️ in Bitcoin Design Guide Roadmap 🎨🎯on Dec 13, 2021
  11. changed the title [-]Add ⚡️ `services` page to `Designing Bitcoin products` chapter[/-] [+]Add ⚡️ `Lightning services` page to `Designing Bitcoin products` chapter[/+] on Feb 11, 2022
  12. Repository owner moved this from Todo 📝 to Done ✅ in Bitcoin Design Guide Roadmap 🎨🎯on Apr 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

CopyTask is about improving text.Design bitcoin productsReferring to the Design BTC product section.

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions