From 47d325c6ac50587d9974651a7b2a692f85c9a068 Mon Sep 17 00:00:00 2001 From: neil saitug Date: Mon, 15 Aug 2022 15:16:35 -0500 Subject: [PATCH] gossip: delay considering a channel edge deleted for 12-blocks (#1004) Allows us time to propagate a splice update (new channel_announcement) Suggested-By: @t-bast Co-Authored: @ddustin --- 07-routing-gossip.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/07-routing-gossip.md b/07-routing-gossip.md index f86106523..711734165 100644 --- a/07-routing-gossip.md +++ b/07-routing-gossip.md @@ -224,7 +224,7 @@ The receiving node: - otherwise: - SHOULD store this `channel_announcement`. - once its funding output has been spent OR reorganized out: - - SHOULD forget a channel. + - SHOULD forget a channel after a 12-block delay. ### Rationale @@ -249,6 +249,10 @@ optional) features will have _odd_ feature bits, while incompatible features will have _even_ feature bits (["It's OK to be odd!"](00-introduction.md#glossary-and-terminology-guide)). +A delay of 12-blocks is used when forgetting a channel on funding output spend +as to permit a new `channel_announcement` to propagate which indicates this +channel was spliced. + ## The `node_announcement` Message This gossip message allows a node to indicate extra data associated with it, in