From eef93129653812ed6727d11c8b42c07c774b2155 Mon Sep 17 00:00:00 2001 From: Rusty Russell Date: Tue, 18 Jul 2023 06:59:33 +0930 Subject: [PATCH] BOLT 2: fix battling requirements for `shutdown` The shutdown section says: ``` - MUST NOT send multiple `shutdown` messages. ``` But the reconnection section says: ``` - upon reconnection: - if it has sent a previous `shutdown`: - MUST retransmit `shutdown`. ``` So clearly, remove the former. Signed-off-by: Rusty Russell --- 02-peer-protocol.md | 1 - 1 file changed, 1 deletion(-) diff --git a/02-peer-protocol.md b/02-peer-protocol.md index 353ad74..324ddd9 100644 --- a/02-peer-protocol.md +++ b/02-peer-protocol.md @@ -1555,7 +1555,6 @@ A sending node: - MAY send a `shutdown` before a `channel_ready`, i.e. before the funding transaction has reached `minimum_depth`. - if there are updates pending on the receiving node's commitment transaction: - MUST NOT send a `shutdown`. - - MUST NOT send multiple `shutdown` messages. - MUST NOT send an `update_add_htlc` after a `shutdown`. - if no HTLCs remain in either commitment transaction (including dust HTLCs) and neither side has a pending `revoke_and_ack` to send: