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