From 4b62d26af93a07166d6a9de2cb5eff80849d9c19 Mon Sep 17 00:00:00 2001 From: Rusty Russell Date: Mon, 23 Jul 2018 21:14:59 +0930 Subject: [PATCH] BOLT 2: fix placement of chain_hash requirement. Reported-by: Matthias Grundmann @mattias-g Fixes: #453 Signed-off-by: Rusty Russell --- 02-peer-protocol.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/02-peer-protocol.md b/02-peer-protocol.md index 61e2d60..f9b14bf 100644 --- a/02-peer-protocol.md +++ b/02-peer-protocol.md @@ -204,6 +204,7 @@ The receiving node MAY fail the channel if: - it considers `dust_limit_satoshis` too small and plans to rely on the sending node publishing its commitment transaction in the event of a data loss (see [message-retransmission](02-peer-protocol.md#message-retransmission)). The receiving node MUST fail the channel if: + - the `chain_hash` value is set to a hash of a chain that is unknown to the receiver. - `push_msat` is greater than `funding_satoshis` * 1000. - `to_self_delay` is unreasonably large. - `max_accepted_htlcs` is greater than 483. @@ -280,9 +281,6 @@ avoid double-spending of the funding transaction. - MUST set `dust_limit_satoshis` less than or equal to `channel_reserve_satoshis` from the `open_channel` message. The receiver: - - if the `chain_hash` value, within the `open_channel`, message is set to a hash - of a chain that is unknown to the receiver: - - MUST reject the channel. - if `minimum_depth` is unreasonably large: - MAY reject the channel. - if `channel_reserve_satoshis` is less than `dust_limit_satoshis` within the `open_channel` message: