📅 Original date posted:2021-04-28
📝 Original message:
On Mon, Dec 07, 2020 at 11:32:27AM +1100, Lloyd Fournier wrote:
> I've been considering the problem of recovering lightning channels after
> losing channel state in a boating accident. The modern way of doing this
> seems to be "static channel backups" -- these are essentially lists of
> channel ids and the nodes you had the channels with.
>
> The idea is that with this backup you can remember who you had channels
> with, connect to them and ask them to force close the channel (can someone
> link me the concrete protocol messages you send to do this?).
>
> It occurred to me that if the lightning protocol were changed slightly you
> could do this without the channel backup at all.
I was re-reading this OP after seeing some of Rusty's concerns later in
the thread and I was wondering why we need to alter funding at all.
We're assuming that when Alice recovers from her backup, she knows her
node_id and has the private key necessary to sign messages for it, so
why can't she sign a message that gets gossiped across the network that
says, "if you have a channel with node_id 0xa11ce, please close it now"?
Maybe the message also includes a signed timestamp or block height so
only channels with funding transactions confirmed before that
time/height get closed, preventing future replays of the message from
closing Alice's later channels opened with the same seed/node_id.
-Dave
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20210428/14422f93/attachment.sig>;
David A. Harding [ARCHIVE] /
npub16d…x4wrd
2023-06-09 13:02:17
in reply to nevent1q…hmnp
Author Public Key
npub16dt55fpq3a8r6zpphd9xngxr46zzqs75gna9cj5vf8pknyv2d7equx4wrdPublished at
2023-06-09 13:02:17Event JSON
{
"id": "e93b2222b67269c626e836b212301b298909dbee5b19b8474612e1aa3dde1019",
"pubkey": "d3574a24208f4e3d0821bb4a69a0c3ae842043d444fa5c4a8c49c369918a6fb2",
"created_at": 1686315737,
"kind": 1,
"tags": [
[
"e",
"9eb4c7be3b2b54415d1ca222464abf2f2c946db286a895ee30cb6529f9bcf7b5",
"",
"root"
],
[
"e",
"06242941a490af300ca41b9467a4178484c87a6cd1a435da9640fc4acbdb363c",
"",
"reply"
],
[
"p",
"13bd8c1c5e3b3508a07c92598647160b11ab0deef4c452098e223e443c1ca425"
]
],
"content": "📅 Original date posted:2021-04-28\n📝 Original message:\nOn Mon, Dec 07, 2020 at 11:32:27AM +1100, Lloyd Fournier wrote:\n\u003e I've been considering the problem of recovering lightning channels after\n\u003e losing channel state in a boating accident. The modern way of doing this\n\u003e seems to be \"static channel backups\" -- these are essentially lists of\n\u003e channel ids and the nodes you had the channels with.\n\u003e \n\u003e The idea is that with this backup you can remember who you had channels\n\u003e with, connect to them and ask them to force close the channel (can someone\n\u003e link me the concrete protocol messages you send to do this?).\n\u003e \n\u003e It occurred to me that if the lightning protocol were changed slightly you\n\u003e could do this without the channel backup at all.\n\nI was re-reading this OP after seeing some of Rusty's concerns later in\nthe thread and I was wondering why we need to alter funding at all.\nWe're assuming that when Alice recovers from her backup, she knows her\nnode_id and has the private key necessary to sign messages for it, so\nwhy can't she sign a message that gets gossiped across the network that\nsays, \"if you have a channel with node_id 0xa11ce, please close it now\"?\n\nMaybe the message also includes a signed timestamp or block height so\nonly channels with funding transactions confirmed before that\ntime/height get closed, preventing future replays of the message from\nclosing Alice's later channels opened with the same seed/node_id.\n\n-Dave\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 833 bytes\nDesc: not available\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20210428/14422f93/attachment.sig\u003e",
"sig": "e80c2b7072aa906ec27fbf080f8a268e5e8d72fc64842b9356a1f3610184a42ef436ea2b326ea022b54251bd463eed1c63ffa1a655b25a7396978d1afc398f3f"
}