Nicolas Dorier [ARCHIVE] on Nostr: 📅 Original date posted:2017-02-07 📝 Original message: Good point, actually, a ...

📅 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>;