You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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
changed the title [-]Add `Lightning services` page to `Designing Bitcoin products` chapter[/-][+]Add ⚡️ `services` page to `Designing Bitcoin products` chapter[/+]on Nov 7, 2021
changed the title [-]Add ⚡️ `services` page to `Designing Bitcoin products` chapter[/-][+]Add ⚡️ `Lightning services` page to `Designing Bitcoin products` chapter[/+]on Feb 11, 2022
Activity
johnsBeharry commentedon Oct 19, 2021
Concept ACK. It also is a good idea to model it after the tech primer.
Inbound liquidity*
Lighting Terminal
Amboss, LN+
pavlenex commentedon Oct 19, 2021
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.
kingonly commentedon Oct 22, 2021
Suggest to use zero-conf channels instead of turbo channels. We don't need an extra marketing layer to describe the tech.
[-]Add `Lightning service providers` page to `Designing Bitcoin products` chapter[/-][+]Add `Lightning services` page to `Designing Bitcoin products` chapter[/+][-]Add `Lightning services` page to `Designing Bitcoin products` chapter[/-][+]Add ⚡️ `services` page to `Designing Bitcoin products` chapter[/+]pavlenex commentedon Nov 15, 2021
@Bosch-0 is this something we'd still want to tackle in the Milestone #10 or should we postpone it for later revision?
Bosch-0 commentedon Nov 16, 2021
@pavlenex How's about we include it in the next milestone so we can wrap up 10 :)
[-]Add ⚡️ `services` page to `Designing Bitcoin products` chapter[/-][+]Add ⚡️ `Lightning services` page to `Designing Bitcoin products` chapter[/+]