📅 Original date posted:2018-01-02
📝 Original message:
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 [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 [Lightning-dev at lists.linuxfoundation.org]
https://lists.linuxfoundation. org/mailman/listinfo/ lightning-dev [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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20180102/f5facf90/attachment.html>;
Johan Torås Halseth [ARCHIVE] /
npub1pp…hs2fw
2023-06-09 14:48:20
in reply to nevent1q…dnne
Author Public Key
npub1ppn2nhlfdzkw9gw0ytljpef5dpyzsxzw8ffcyykamt32hw6pge0smhs2fwPublished at
2023-06-09 14:48:20Event JSON
{
"id": "5d186af303ee9bc68bcd0a83c97fe5545319352d2e131a6ec2fa6dc740444ed5",
"pubkey": "0866a9dfe968ace2a1cf22ff20e534684828184e3a538212dddae2abbb41465f",
"created_at": 1686314900,
"kind": 1,
"tags": [
[
"e",
"ee356e7264fbfd4e1ae93e9714e20beb5f1fd1d4a8f5b334b7932ea89820344d",
"",
"root"
],
[
"e",
"c41bb2a75861da18f6a18283436fb615906601cd30ada05b53adda72570e24bf",
"",
"reply"
],
[
"p",
"f3efacfe11c2dfac927215bab9d73ea1852dbaa67af99ccaec4768c4fada71a2"
]
],
"content": "📅 Original date posted:2018-01-02\n📝 Original message:\nHi,\nBefore 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.\n\nCheers, Johan\nOn Tue, Jan 2, 2018 at 15:11, Hafeez Bana \u003chafeez.bana at gmail.com\u003e wrote:\nto fix transaction malleability\n\nOn Tue, Jan 2, 2018 at 1:53 PM, Praveen Baratam \u003c praveen.baratam at gmail.com [praveen.baratam at gmail.com] \u003e wrote:\nWhy 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...\nI don't see how SegWit is important here... Am I missing something?\n\n--\nDr. Praveen Baratam\nabout.me [http://about.me/praveen.baratam] ᐧ\n______________________________ _________________\nLightning-dev mailing list\nLightning-dev at lists. linuxfoundation.org [Lightning-dev at lists.linuxfoundation.org]\nhttps://lists.linuxfoundation. org/mailman/listinfo/ lightning-dev [https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev]\n\n\n\n_______________________________________________ Lightning-dev mailing list Lightning-dev at lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20180102/f5facf90/attachment.html\u003e",
"sig": "a7f5dec482d6f6c491cb8c41d1967714a4d76664d06dddc06815a6b145ffc657bf1e318b90d0d13c701fd315edf14c49e7700040891e7fddb4100c625f652497"
}