Present the full range of capabilities LSPs can have and which at minimum they need to support

[johnsBeharry]

Currently the LSP page just outlines 3 capabiltiies a LSP could have. Often these systems are referred to as something monolithic, but there may also be an opportunity for some of the service capabilities to be offered standalone.

An LSP, we loosely define it as a service that provides the end users with capabilities that support their connection to the lightning network which lives outside of the wallet, and may have some monetisation strategy.

From a conversation with @Bosch-0 he mentioned LSPs should have some minimum set of capabilities. With that loose definition of what an LSP is, does it make sense to have a set of core capabilities all LSPs should have? Alternatively should we go up a level, and categorise different LSPs by type?

Here's a list of some of the possible capabilities

• Liquidity provisioning
• Don't have to be online all the time (Phoenix)
• Backups of state
• Recovery
• Calculating payment paths
• Watch tower
• Submarine swaps

Are there others? Which are absolutely required, necessary for mainstream persons ux, and nice add-ons?

[Bosch-0]

Could add services like Amboss and LN+ - not sure what to categorize them as though. They're more like 'meta Lightning services' as they aren't things that are enacted on the protocol level.

Also just added this issue to the Bitcoin Design Guide repo:

• https://github.com/BitcoinDesign/Guide/issues/532

[johnsBeharry]

Could add services like Amboss and LN+ - not sure what to categorize them as though. They're more like 'meta Lightning services' as they aren't things that are enacted on the protocol level.

Mentioned on that issue that I see them LSP Directories and LN+ is a platform to allow anyone offer lightning services (inbound liquidity). Thats actually a perfect hackathon project, especially if Alby the extension and WebLN would support lnurl-channel.

REF

• https://github.com/peakshift/bolt.fun/issues/11