1061 sats \ 7 replies \ @hampus 8 Jan 2023 \ on: Is LND (Lightning Labs) ruining the Lighting Network? bitcoin
This is a very popular narrative, but it's just not true.
Lnd is collaborating with the rest, including on some of the things you listed in the post. As an example, BOLT12 is actively being developed for Lnd by Carla Kirk-Cohen, an ex-Lightning Labs employee.
LN node devs have weekly meetings where the BOLT-specification is being discussed. You would find that the narrative that it's "Lnd's way or the highway" is just not true, if you actually did some digging.
Anyway, all LN node companies have their own fair share of Conflict of Interest. I don't see you complaining that ACINQ went proprietary with their 0-conf channel feature for their own Phoenix Wallet. A feature that all LN node implementations and wallets would benefit from. It took years before Rusty went on to do it the right way (thank you for that) and make it into the BOLT-specification. Features option_scid_alias and option_zeroconf are now supported in all big LN node implementations. A success story.
My point with this that it's not just "lnd bad, the rest good". It's childish to think like that. There is some dirt everywhere.
write
preview
232 sats \ 5 replies \ @TonyGiorgio 9 Jan 2023
I think the fact that an ex employee of LL and not LL itself still shows LL's priorities here. You aren't seeing them care about Bolt12 in fact they are pretty actively against it.
Also I can tell you from experience that zeroconf integrations are dog shit and very much not a success story.
reply
30 sats \ 4 replies \ @hampus 9 Jan 2023
I think the fact that an ex employee of LL and not LL itself still shows LL's priorities here. You aren't seeing them care about Bolt12 in fact they are pretty actively against it.
Yes. You don't decide what other people do with their time. Lightning Labs is not holding back BOLT12 as claimed in the OP. It's as far as I can tell approved for inclusion to lnd.
You can read more here: https://github.com/lightningnetwork/lnd/issues/5594#issuecomment-1150822223
Also I can tell you from experience that zeroconf integrations are dog shit and very much not a success story.
Yes, you go ahead and shit other people's hard work. That's really nice of you. I'm sure you're a super developer.
The point was to show that lnd is indeed collaborating with the rest.
reply
10 sats \ 3 replies \ @TonyGiorgio 9 Jan 2023
Yes, you go ahead and shit other people's hard work. That's really nice of you. I'm sure you're a super developer.
You call it a success story, it's not. Sorry that hit a touch spot for you.
The point was to show that lnd is indeed collaborating with the rest.
Perhaps you've never tried to open a zero conf channel with LND to another implementation. Or perhaps you've never tried to accept a zero conf channel with LND from another implementation. Maybe you should try it before calling it a success story. Sure, they collaborate, but this is a terrible example.
reply
20 sats \ 2 replies \ @hampus 9 Jan 2023
You call it a success story, it's not. Sorry that hit a touch spot for you.
Yes, it's a success story if you stick to the topic, which is node implementation collaboration.
Perhaps you've never tried to open a zero conf channel with LND to another implementation. Or perhaps you've never tried to accept a zero conf channel with LND from another implementation. Maybe you should try it before calling it a success story. Sure, they collaborate, but this is a terrible example.
Stick to the topic.
reply
0 sats \ 1 reply \ @TonyGiorgio 9 Jan 2023
They collaborated and failed, okay great example. Thanks for the conversations and confirmation.
reply
20 sats \ 0 replies \ @hampus 9 Jan 2023
Bruh. What is your problem? It's one example of a collaboration out of many. It was meant to show that it's just pure FUD that lnd isn't involved in the BOLT process.
And it's not a failed collaboration. Issues are actively being addressed.
reply
20 sats \ 0 replies \ @vnprc 9 Jan 2023 freebie
You counterexample is bunk. Carla is not a LL employee and even if she was, that repo hasn't seen any activity in months.
reply