while i agree that LN is a pretty complicated beast one could also argue that bitcoin has been around for 14 years and UX in most software is far from where we would want it to be - by a long shot

While solving LN problems is far from fast, underfunded ecosystem and complexity don't help, things are being built that make lightning much more seamless for people - we have phoenix with splicing now simplifying, breez with greenlight making self custodial nodes super lightweight and integrating lightning into apps a breeze. LSP spec unifying liquidity markets and enabling compatibility across solutions.

nostr:nevent1qqsv5jyfh9gp2qnhruevrph39s2mspzfw3e9mx5avg0wenltrdjnnhgpr3mhxue69uhkummnw3ezuumhd9ehxtt9de5kwmtp9e3kstczyrzum4tn0erl2snvnh4zgvqjzyhdvta60df50zrgzcr00866h95z5qcyqqqqqqg96kh8z

Reply to this note

Please Login to reply.

Discussion

Btw I have questions to both greenlight and economical side of LSP idea.

For greenlight, as far as I understand it outsources channel updates signing and refund destinations, but it should be able to do things like:

- publish an old channel state and let peer take all the funds (peer is greenlight).

- do nothing for long enough when peer publishes an old channel state and let them take all the funds.

If we trust them not to, this is a custodial solution.

For LSP, I would really like to know how well do current ones do and how much payment activity per channel on average do they need to be profitable.

Greenlight is not the peer, you can open chans to whichever peer you want

Watchtower can solve the second

Watchtower cannot undo the publishing of an old state. It can only publish justice transactions.

nostr:npub1ykgzq83frx525etgezysqxf25480qrnvp962tvzr9afxzj5yrmyqp3mpsh that was meant to be an answer to a second point about peer publishing an old state and your node not being woken up

Ah, my mistake

You can't solve the first though, which is the worst.