Christopher Jamthagen [ARCHIVE] on Nostr: 📅 Original date posted:2015-08-01 📝 Original message: > Sent: Saturday, August ...
📅 Original date posted:2015-08-01
📝 Original message:
> Sent: Saturday, August 01, 2015 at 11:57 AM
> From: "Eric Lombrozo" <elombrozo at gmail.com>
> To: "Rusty Russell" <rusty at rustcorp.com.au>
> Cc: "Christopher Jamthagen" <cjamthagen at gmx.com>, "lightning-dev at lists.linuxfoundation.org" <lightning-dev at lists.linuxfoundation.org>
> Subject: Re: [Lightning-dev] Stealing money from a hub?
> On Jul 30, 2015, at 4:48 PM, Rusty Russell <rusty at rustcorp.com.au> wrote:
> But I realized yesterday, outsourcing needs a new sighash op mode (or
> normalized txids), so it's not really something to design a deployable
> system around today.
> Can you elaborate on this, Rusty?
We wont know the txid of the revoked commitment transaction until the cheater signs and broadcasts it, thus we cannot pre-sign the stealing transaction for the third party.
📝 Original message:
> Sent: Saturday, August 01, 2015 at 11:57 AM
> From: "Eric Lombrozo" <elombrozo at gmail.com>
> To: "Rusty Russell" <rusty at rustcorp.com.au>
> Cc: "Christopher Jamthagen" <cjamthagen at gmx.com>, "lightning-dev at lists.linuxfoundation.org" <lightning-dev at lists.linuxfoundation.org>
> Subject: Re: [Lightning-dev] Stealing money from a hub?
> On Jul 30, 2015, at 4:48 PM, Rusty Russell <rusty at rustcorp.com.au> wrote:
> But I realized yesterday, outsourcing needs a new sighash op mode (or
> normalized txids), so it's not really something to design a deployable
> system around today.
> Can you elaborate on this, Rusty?
We wont know the txid of the revoked commitment transaction until the cheater signs and broadcasts it, thus we cannot pre-sign the stealing transaction for the third party.