What is Nostr?
Praveen Baratam [ARCHIVE] /
npub14sz…v9e3
2023-06-09 12:48:21
in reply to nevent1q…q708

Praveen Baratam [ARCHIVE] on Nostr: 📅 Original date posted:2018-01-02 📝 Original message: Which is the most mature ...

📅 Original date posted:2018-01-02
📝 Original message:
Which is the most mature Lightning implementation right now? I want to
setup a lightning node and start experimenting with it.

Also did anybody create a protocol diagram of how lightning works? (similar
to the one below about SSL)

[image: Inline image 1]

I have seen higher level diagrams but as evident from my previous mails,
they only touch the basic concepts and not the exact flow of events leaving
many doubts. It would be really helpful to make such a detailed
flowchart/diagram if one does not exist already.

Also, what are the current limitations/known-gaps in lightening network
protocol? When can its guarantees fail?


On Tue, Jan 2, 2018 at 8:13 PM, Johan Torås Halseth <johanth at gmail.com>
wrote:

> That’s correct :)
>
> On Tue, Jan 2, 2018 at 15:34, Praveen Baratam <praveen.baratam at gmail.com>
> wrote:
>
> Thank you for explaining @Hafeez & @Johan
>
> Now that all the BIPs necessary for LN including SegWit (Softfork) are
> active on the mainnet, are we just waiting for the LN implementation to
> mature or are there any other issues?
> ᐧ
>
> On Tue, Jan 2, 2018 at 8:01 PM, Johan Torås Halseth <johanth at gmail.com>
> wrote:
>
>> Hi,
>>
>> Before you can safely broadcast the funding transaction, the two parties
>> involved in a channel must have signed a commitment transaction spending
>> the output from the funding transaction. Without segwit, the funding
>> transaction can be malleated, leaving the commitment transaction invalid,
>> and funds locked up if one of the parties stops cooperating.
>>
>> Cheers,
>> Johan
>> On Tue, Jan 2, 2018 at 15:11, Hafeez Bana <hafeez.bana at gmail.com> wrote:
>>
>> to fix transaction malleability
>>
>> On Tue, Jan 2, 2018 at 1:53 PM, Praveen Baratam <
>> praveen.baratam at gmail.com> wrote:
>>
>>> Why is SegWit required for LN? If we wait for the *funding transaction*
>>> to be *confirmed*, we can then safely create and update unconfirmed
>>> commitment transactions...
>>>
>>> I don't see how SegWit is important here... Am I missing something?
>>>
>>> --
>>> Dr. Praveen Baratam
>>>
>>> about.me <http://about.me/praveen.baratam>;
>>> ᐧ
>>>
>>> _______________________________________________
>>> Lightning-dev mailing list
>>> Lightning-dev at lists.linuxfoundation.org
>>> https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
>>>
>>>
>>
>> _______________________________________________ Lightning-dev mailing
>> list Lightning-dev at lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
>>
>>
>
>
> --
> Dr. Praveen Baratam
>
> about.me <http://about.me/praveen.baratam>;
>
>


--
Dr. Praveen Baratam

about.me <http://about.me/praveen.baratam>;
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20180102/95ab9cd8/attachment-0001.html>;
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 35857 bytes
Desc: not available
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20180102/95ab9cd8/attachment-0001.png>;
Author Public Key
npub14sz60zalvsz094ekxmgq2xpcsr67a9aljeqcny479lc8mpsp95jqfwv9e3