{"type":"rich","version":"1.0","title":"Bastien TEINTURIER [ARCHIVE] wrote","author_name":"Bastien TEINTURIER [ARCHIVE] (npub17f…ntr0s)","author_url":"https://yabu.me/npub17fjkngg0s0mfx4uhhz6n4puhflwvrhn2h5c78vdr5xda4mvqx89swntr0s","provider_name":"njump","provider_url":"https://yabu.me","html":"📅 Original date posted:2021-06-30\n📝 Original message:\n\u003e\n\u003e - MUST NOT send `announcement_signatures` messages until `funding_locked`\n\u003e       has been sent and received AND the funding transaction has at least\n\u003e six confirmations.\n\u003e\n\u003e So still compliant there?\n\u003e\n\nGreat, I hadn't spotted that one, so we're good on the\n`announcement_signatures` side.\n\nI'm wondering if `option_zeroconf` implies that we should set `min_depth =\n0` in\n`accept_channel`, since that's the number of confirmations before we can\nsend\n`funding_locked`.\n\nWe need a signal that this channel uses zero-conf, and the two obvious\nchoices are:\n\n   - set `min_depth = 0`\n   - use a `channel_type` that sets `option_zeroconf`\n\nI think the second option is better, this way we can keep a \"normal\"\n`min_depth` set\nand when we send `funding_locked`, we know that the channel is now\nperfectly safe\nto use (out of the zero-conf zone).\n\nCheers,\nBastien\n\n\n\nLe mer. 30 juin 2021 à 02:09, Rusty Russell \u003crusty at rustcorp.com.au\u003e a\nécrit :\n\n\u003e Bastien TEINTURIER \u003cbastien at acinq.fr\u003e writes:\n\u003e \u003e Hi Rusty,\n\u003e \u003e\n\u003e \u003e On the eclair side, we instead send `funding_locked` as soon as we\n\u003e \u003e see the funding tx in the mempool.\n\u003e \u003e\n\u003e \u003e But I think your proposal would work as well.\n\u003e\n\u003e This would be backward compatible, I think.  Eclair would send\n\u003e `funding_locked`, which is perfectly legal, but a normal peer would\n\u003e still wait for confirms before also sending `funding_locked`; it's\n\u003e just that option_zeroconf_channels would mean it doesn't have to\n\u003e wait for that before sending HTLCs?\n\u003e\n\u003e \u003e We may want to defer sending `announcement_signatures` until\n\u003e \u003e after the funding tx has been confirmed? What `min_depth` should\n\u003e \u003e we use here? Should we keep a non-zero value in `accept_channel`\n\u003e \u003e or should it be zero?\n\u003e\n\u003e You can't send it before you know the channel_id, so it has to be at\n\u003e least 1.  Spec says:\n\u003e\n\u003e       - MUST NOT send `announcement_signatures` messages until\n\u003e `funding_locked`\n\u003e       has been sent and received AND the funding transaction has at least\n\u003e six confirmations.\n\u003e\n\u003e So still compliant there?\n\u003e\n\u003e Cheers,\n\u003e Rusty.\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20210630/f022c575/attachment.html\u003e"}