1f52b on Nostr: Been thinking about this a bit -- *perhaps*, one of the reasons Lightning has taken ...
Been thinking about this a bit -- *perhaps*, one of the reasons Lightning has taken so long is that we're only just realising how important the LSP component is. Wallets/nodes that work with a LSP are so much easier to run and use for non-dev and non-in-it-as-a-business people. Even as a dev, I'm fairly hesitant to sign myself up for the maintenance effort of running a normal Lightning node.
Things like Phoenix,
ZEUS (npub1xnf…lpr5), Phoenixd and
OpenSecret (npub1mut…23vg) (mutiny server soon! 👀) are just so much easier to work with than "just" run LND/Eclair/C-Lightning/LDK-Node etc. Is the logical conclusion that for Lightning node-running to become prolific, LSPs (or more accurately, a way for nodes to 'buy' inbound from and get channels with others) have to become an inherent part of the Lightning protocol? Feels like it to me.
Let’s be clear, if no one steps up and decides to run LSPs because everyone is worried about regulatory concerns, every bitcoin L2 system is toast - every one that has a reasonable security model relies on some kind of centralized or federated party that has similar concerns, even if they can’t seize funds.
Without any L2 systems everyone using bitcoin will simply use custodial platforms because that’s the only way to get reasonable fees and payment latency.
And don’t go yelling at ACINQ for deciding not to operate Phoenix in the US, the software required to run an LSP is open source, with only relatively minimal liquidity allocation logic required to get started. We need new entrants, and that means new companies who think the risk is manageable (I’m confident it is, but I can’t fault anyone for not wanting to take that risk).
If you see someone suggesting ACINQ should just keep running, the correct response is “well why aren’t you running an LSP”.
Published at
2024-04-29 18:50:53Event JSON
{
"id": "000004f711160e03f654bd0f676fe897acd5f2902c564403843581832b6aeaf4",
"pubkey": "1f52b16e5ca201ef2dc030f9b651137672e52de1ab29c0b0f6b72ac80ab23c84",
"created_at": 1714416653,
"kind": 1,
"tags": [
[
"p",
"34d2f5274f1958fcd2cb2463dabeaddf8a21f84ace4241da888023bf05cc8095"
],
[
"p",
"df173277182f3155d37b330211ba1de4a81500c02d195e964f91be774ec96708"
],
[
"q",
"3dc5b00436e7355beadc0001ddb479e455c99424a01f6938143fb8dd7dca0a48",
"wss://nos.lol/"
],
[
"nonce",
"11858621190242104407",
"21"
]
],
"content": "Been thinking about this a bit -- *perhaps*, one of the reasons Lightning has taken so long is that we're only just realising how important the LSP component is. Wallets/nodes that work with a LSP are so much easier to run and use for non-dev and non-in-it-as-a-business people. Even as a dev, I'm fairly hesitant to sign myself up for the maintenance effort of running a normal Lightning node.\n\nThings like Phoenix, nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5, Phoenixd and nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg (mutiny server soon! 👀) are just so much easier to work with than \"just\" run LND/Eclair/C-Lightning/LDK-Node etc. Is the logical conclusion that for Lightning node-running to become prolific, LSPs (or more accurately, a way for nodes to 'buy' inbound from and get channels with others) have to become an inherent part of the Lightning protocol? Feels like it to me.\n\nnostr:nevent1qqsrm3dsqsmwwd2matwqqqwak3u7g4wfjsj2q8mf8q2rlwxa0h9q5jqppemhxue69uhkummn9ekx7mp0dv67jn",
"sig": "f626cd6711666abb416ec91cdb0d19cebeba4f329975a2011e8831376ea5314306d7375c7bd1ee2211f9157b66305b88bde3b9f6371c23a308facfe65c27067b"
}