From 6e85df448bfee7d10f26aabb06b8eba3d7505888 Mon Sep 17 00:00:00 2001 From: ProofOfKeags Date: Mon, 28 Aug 2023 06:13:59 -0600 Subject: [PATCH] BOLT2: change "reject" to "fail" in channel opening requirements (#1104) Since "reject" isn't defined anywhere in the spec and "fail" does have a definition laid out in BOLT1 that includes special provisions for channels that have not yet been established, BOLT2 is amended to clarify the requirements for the receiver of `accept_channel` --- 02-peer-protocol.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/02-peer-protocol.md b/02-peer-protocol.md index b552fad..b7ed62d 100644 --- a/02-peer-protocol.md +++ b/02-peer-protocol.md @@ -363,15 +363,15 @@ The sender: The receiver: - if `minimum_depth` is unreasonably large: - - MAY reject the channel. + - MAY fail the channel. - if `channel_reserve_satoshis` is less than `dust_limit_satoshis` within the `open_channel` message: - - MUST reject the channel. + - MUST fail the channel. - if `channel_reserve_satoshis` from the `open_channel` message is less than `dust_limit_satoshis`: - - MUST reject the channel. + - MUST fail the channel. - if `channel_type` is set, and `channel_type` was set in `open_channel`, and they are not equal types: - - MUST reject the channel. + - MUST fail the channel. - if `option_channel_type` was negotiated but the message doesn't include a `channel_type`: - - MAY reject the channel. + - MAY fail the channel. Other fields have the same requirements as their counterparts in `open_channel`.