From 2d6759b2ca2c2d4e497647d1f81910010174c29a Mon Sep 17 00:00:00 2001 From: t-bast Date: Mon, 3 Oct 2022 10:41:17 +0200 Subject: [PATCH] Bolt 7: restore htlc_maximum_msat requirement Requirements for the htlc_maximum_msat field in channel_update were inadvertently removed by #999 (this PR meant to make this field mandatory, not removed explanations about what it does). --- 07-routing-gossip.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/07-routing-gossip.md b/07-routing-gossip.md index 711734165..66607a448 100644 --- a/07-routing-gossip.md +++ b/07-routing-gossip.md @@ -471,6 +471,9 @@ The origin node: - MUST set the `direction` bit of `channel_flags` to 0. - otherwise: - MUST set the `direction` bit of `channel_flags` to 1. + - MUST set `htlc_maximum_msat` to the maximum value it will send through this channel for a single HTLC. + - MUST set this to less than or equal to the channel capacity. + - MUST set this to less than or equal to `max_htlc_value_in_flight_msat` it received from the peer. - MUST set `must_be_one` in `message_flags` to 1. - MUST set bits in `channel_flags` and `message_flags` that are not assigned a meaning to 0. - MAY create and send a `channel_update` with the `disable` bit set to 1, to