📅 Original date posted:2017-02-07
📝 Original message:
Good point, actually, a simpler way to do it, is for TX2 to be nTimelocked
after bounty's expiration.
If Alice see bob not signing it, she can reclaim the bounty fast.
If bob sign it, Alice can't broadcast it immediately.
On Tue, Feb 7, 2017 at 5:02 AM, Tier Nolan <tier.nolan at gmail.com> wrote:
>
>
> On Mon, Feb 6, 2017 at 4:32 PM, Nicolas Dorier <nicolas.dorier at gmail.com>
> wrote:
>
>> I think you do not need the second timeout.
>>
>> TX2 would be signed by Bob only once he could get back the second Output
>> of TX1.
>>
>
> Alice must have a fully signed version of TX2 before the timeout finishes.
>
> If she doesn't, then Bob can reclaim TX1/1 once the timeout expires and
> then refuse to sign TX2.
>
> If Alice has a signed version of TX2, then she can broadcast it and
> immediately close the channel (claiming TX1/0).
>
> Once that has been accepted, she can then claim TX1/1.
>
>
>
>> So Bob does not have to worry about Alice closing the channel with TX2.
>>
>> Nicolas,
>>
>> _______________________________________________
>> 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/20170207/d4f959a1/attachment.html>;
Nicolas Dorier [ARCHIVE] /
npub1hu…9q4u3
2023-06-09 12:47:01
in reply to nevent1q…kwxq
Author Public Key
npub1huz53hq26gu7nc0qhw3uj6tr9hk5q2ngpywduxep5zy4ay9unftsm9q4u3Published at
2023-06-09 12:47:01Event JSON
{
"id": "8c4047d61280d657b92b5e1e4a3db7e3743540b4a9e142b03c362aea4965a3e3",
"pubkey": "bf0548dc0ad239e9e1e0bba3c969632ded402a68091cde1b21a0895e90bc9a57",
"created_at": 1686314821,
"kind": 1,
"tags": [
[
"e",
"9ea054313bf60f8de6d3bffeb1c78d06c11e96e42cc896b7e3b1ee263032c084",
"",
"root"
],
[
"e",
"88b4b09e5e5b76250d624a3e1b7707d43d562749214cab5494439057a7ce922b",
"",
"reply"
],
[
"p",
"46986f86b97cc97829a031b03209644d134b939d0163375467f0b1363e0d875e"
]
],
"content": "📅 Original date posted:2017-02-07\n📝 Original message:\nGood point, actually, a simpler way to do it, is for TX2 to be nTimelocked\nafter bounty's expiration.\nIf Alice see bob not signing it, she can reclaim the bounty fast.\nIf bob sign it, Alice can't broadcast it immediately.\n\nOn Tue, Feb 7, 2017 at 5:02 AM, Tier Nolan \u003ctier.nolan at gmail.com\u003e wrote:\n\n\u003e\n\u003e\n\u003e On Mon, Feb 6, 2017 at 4:32 PM, Nicolas Dorier \u003cnicolas.dorier at gmail.com\u003e\n\u003e wrote:\n\u003e\n\u003e\u003e I think you do not need the second timeout.\n\u003e\u003e\n\u003e\u003e TX2 would be signed by Bob only once he could get back the second Output\n\u003e\u003e of TX1.\n\u003e\u003e\n\u003e\n\u003e Alice must have a fully signed version of TX2 before the timeout finishes.\n\u003e\n\u003e If she doesn't, then Bob can reclaim TX1/1 once the timeout expires and\n\u003e then refuse to sign TX2.\n\u003e\n\u003e If Alice has a signed version of TX2, then she can broadcast it and\n\u003e immediately close the channel (claiming TX1/0).\n\u003e\n\u003e Once that has been accepted, she can then claim TX1/1.\n\u003e\n\u003e\n\u003e\n\u003e\u003e So Bob does not have to worry about Alice closing the channel with TX2.\n\u003e\u003e\n\u003e\u003e Nicolas,\n\u003e\u003e\n\u003e\u003e _______________________________________________\n\u003e\u003e Lightning-dev mailing list\n\u003e\u003e Lightning-dev at lists.linuxfoundation.org\n\u003e\u003e https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev\n\u003e\u003e\n\u003e\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20170207/d4f959a1/attachment.html\u003e",
"sig": "abb95ca18fcccd462168e2756147db98870aaa48bb4a852975da03735758e14f359cce8c13f383f54577ab3d41e98009f8618c933b61471b0a60de84f6cbd71f"
}