🏷️ Categories: Lightning-dev
quoting naddr1qq…tp8a📝 Summary: The LSPSpec group has created two specifications for Lightning Service Providers to ensure interoperability between Lightning wallets and LSPs. ZmnSCPxj suggests that a common open specification for LSPs could protect client data and allow for provider switching. Wallet implementors should consider implementing client-side interfaces for LSPS specifications, with LSPS0 using a single BOLT8 message ID for all communications.
👥 Authors: • ZmnSCPxj ( ZmnSCPxj [ARCHIVE] (npub1g5z…ms3l) ) • Severin Bühler ( Severin Bühler [ARCHIVE] (npub193u…ftan) )
📅 Messages Date Range: 2023-05-05 to 2023-05-07
✉️ Message Count: 2
📚 Total Characters in Messages: 7377
Messages Summaries
✉️ Message by Severin Bühler on 05/05/2023: The LSPSpec group has developed two mature specifications for Lightning Service Providers to create interoperability between Lightning wallets and LSPs.
✉️ Message by ZmnSCPxj on 07/05/2023: A common open specification for Lightning Service Providers (LSPs) could allow clients to switch between providers and protect their data from potential leaks or breaches. Wallet implementors should consider implementing client-side interfaces for LSPS specifications. LSPS0 uses a single BOLT8 message ID for all LSP communications.
Follow Lightning Mailing List (npub1j3t…4gll) for full threads
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.