📅 Original date posted:2021-06-29
📝 Original message:
Bastien TEINTURIER <bastien at acinq.fr> writes:
> Hi Rusty,
>
> On the eclair side, we instead send `funding_locked` as soon as we
> see the funding tx in the mempool.
>
> But I think your proposal would work as well.
This would be backward compatible, I think. Eclair would send
`funding_locked`, which is perfectly legal, but a normal peer would
still wait for confirms before also sending `funding_locked`; it's
just that option_zeroconf_channels would mean it doesn't have to
wait for that before sending HTLCs?
> We may want to defer sending `announcement_signatures` until
> after the funding tx has been confirmed? What `min_depth` should
> we use here? Should we keep a non-zero value in `accept_channel`
> or should it be zero?
You can't send it before you know the channel_id, so it has to be at
least 1. Spec says:
- MUST NOT send `announcement_signatures` messages until `funding_locked`
has been sent and received AND the funding transaction has at least six confirmations.
So still compliant there?
Cheers,
Rusty.
Rusty Russell [ARCHIVE] /
npub1zw…hkhpx
2023-06-09 12:40:21
in reply to nevent1q…fve2
Author Public Key
npub1zw7cc8z78v6s3grujfvcv3ckpvg6kr0w7nz9yzvwyglyg0qu5sjsqhkhpxPublished at
2023-06-09 12:40:21Event JSON
{
"id": "1503ec3e872e81034a00c2d2e13ed35c7d09af02fb7926a7c423d8dc3ec34b4c",
"pubkey": "13bd8c1c5e3b3508a07c92598647160b11ab0deef4c452098e223e443c1ca425",
"created_at": 1686314421,
"kind": 1,
"tags": [
[
"e",
"f29bcfc2ebeea12d8a0d4f6fa878e2b45ab3505a46bbee55d05cf5e50d60c222",
"",
"root"
],
[
"e",
"1e2a12275ebe8353b9465ae7b7f0d049dc9f32c5123ed47c8e38b9c5130229e7",
"",
"reply"
],
[
"p",
"f26569a10f83f6935797b8b53a87974fdcc1de6abd31e3b1a3a19bdaed8031cb"
]
],
"content": "📅 Original date posted:2021-06-29\n📝 Original message:\nBastien TEINTURIER \u003cbastien at acinq.fr\u003e writes:\n\u003e Hi Rusty,\n\u003e\n\u003e On the eclair side, we instead send `funding_locked` as soon as we\n\u003e see the funding tx in the mempool.\n\u003e\n\u003e But I think your proposal would work as well.\n\nThis would be backward compatible, I think. Eclair would send\n`funding_locked`, which is perfectly legal, but a normal peer would\nstill wait for confirms before also sending `funding_locked`; it's\njust that option_zeroconf_channels would mean it doesn't have to\nwait for that before sending HTLCs?\n\n\u003e We may want to defer sending `announcement_signatures` until\n\u003e after the funding tx has been confirmed? What `min_depth` should\n\u003e we use here? Should we keep a non-zero value in `accept_channel`\n\u003e or should it be zero?\n\nYou can't send it before you know the channel_id, so it has to be at\nleast 1. Spec says:\n\n - MUST NOT send `announcement_signatures` messages until `funding_locked`\n has been sent and received AND the funding transaction has at least six confirmations.\n\nSo still compliant there?\n\nCheers,\nRusty.",
"sig": "f937c8a3e0c49c7ed2acd1026377b1a00dd7ca4f6cb22a605aed22de9d6b95e833a2a3a602e5f53c07120b57c35ddcac38fe8e46bb36226b859aa1c959526d24"
}