📅 Original date posted:2016-03-07 📝 Original message: Ok, got my answer from ...

Fabrice Drouin [ARCHIVE] /

npub1s8z…yaw4

2023-06-09 12:45:51

in reply to nevent1q…smm2

📅 Original date posted:2016-03-07
📝 Original message:
Ok, got my answer from the thread you started on deterministic R values
and which I had missed :)

On 7 March 2016 at 20:09, Fabrice Drouin <fabrice.drouin at acinq.fr> wrote:
> Hi,
> I may have misunderstood something, but with this scheme instead of R
> + shachain/elkrem, then how do nodes react when old commit tx are
> published ? It seems that they would have to store lots of signatures
> ?
>
>
> On 7 March 2016 at 08:28, Nicolas Dorier <nicolas.dorier at gmail.com> wrote:
>> I managed to adapt the payment channel script to use less space.
>>
>> This version is winning around 32 bytes in the scriptpubkey (for the R
>> value) as well as 70 bytes in the signature when Alice close the channel.
>>
>> Alice closing the channel:
>> http://n.bitcoin.ninja/checkscript?savedScript=51225750-f245-45b5-a86c-6ca1e87dcafb
>>
>> Bob using revocation:
>> http://n.bitcoin.ninja/checkscript?savedScript=c4d7ebaa-5a79-4c03-ab55-c499854f1e94
>>
>> This amount to 100 bytes saved between the anchor transaction + commitment
>> broadcasted.
>>
>> _______________________________________________
>> Lightning-dev mailing list
>> Lightning-dev at lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
>>

Author Public Key

npub1s8zghfrvyydu3ld5jrgue7crvzw8agyslpv8mh9pexgxwmcfelfsk5yaw4

Seen on

wss://relay.nostr.band

Show more details

Published at

2023-06-09 12:45:51

Kind type

1 Short Text Note

Event JSON

{ "id": "bccc5ddec311029bb4a5bf9954e163540138c94ecd8a04f3795231ca2747b4d1", "pubkey": "81c48ba46c211bc8fdb490d1ccfb03609c7ea090f8587ddca1c990676f09cfd3", "created_at": 1686314751, "kind": 1, "tags": [ [ "e", "9dffd851f36e0464b9b84a18f034d9a166bd96caa924994430620e4b51393055", "", "root" ], [ "e", "04dfe55381697f5361e367d0089fb86be4fb8180f9e71c236a9d7839766132cf", "", "reply" ], [ "p", "81c48ba46c211bc8fdb490d1ccfb03609c7ea090f8587ddca1c990676f09cfd3" ] ], "content": "📅 Original date posted:2016-03-07\n📝 Original message:\nOk, got my answer from the thread you started on deterministic R values\nand which I had missed :)\n\nOn 7 March 2016 at 20:09, Fabrice Drouin \u003cfabrice.drouin at acinq.fr\u003e wrote:\n\u003e Hi,\n\u003e I may have misunderstood something, but with this scheme instead of R\n\u003e + shachain/elkrem, then how do nodes react when old commit tx are\n\u003e published ? It seems that they would have to store lots of signatures\n\u003e ?\n\u003e\n\u003e\n\u003e On 7 March 2016 at 08:28, Nicolas Dorier \u003cnicolas.dorier at gmail.com\u003e wrote:\n\u003e\u003e I managed to adapt the payment channel script to use less space.\n\u003e\u003e\n\u003e\u003e This version is winning around 32 bytes in the scriptpubkey (for the R\n\u003e\u003e value) as well as 70 bytes in the signature when Alice close the channel.\n\u003e\u003e\n\u003e\u003e Alice closing the channel:\n\u003e\u003e http://n.bitcoin.ninja/checkscript?savedScript=51225750-f245-45b5-a86c-6ca1e87dcafb\n\u003e\u003e\n\u003e\u003e Bob using revocation:\n\u003e\u003e http://n.bitcoin.ninja/checkscript?savedScript=c4d7ebaa-5a79-4c03-ab55-c499854f1e94\n\u003e\u003e\n\u003e\u003e This amount to 100 bytes saved between the anchor transaction + commitment\n\u003e\u003e broadcasted.\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", "sig": "d1d5a3ca3d0db9e1f2e9b05970738d79b5e4f9fd6c28d09eda3b1392e3608be377b367cc785d0941c8f3ffd675d375bf2302fa68647596f7586e003c36da73a3" }