{"type":"rich","version":"1.0","title":"Rusty Russell [ARCHIVE] wrote","author_name":"Rusty Russell [ARCHIVE] (npub1zw…hkhpx)","author_url":"https://yabu.me/npub1zw7cc8z78v6s3grujfvcv3ckpvg6kr0w7nz9yzvwyglyg0qu5sjsqhkhpx","provider_name":"njump","provider_url":"https://yabu.me","html":"📅 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."}