Skip to content

Commit

Permalink
Bolt 7: restore htlc_maximum_msat requirement (#1029)
Browse files Browse the repository at this point in the history
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).
  • Loading branch information
t-bast authored Oct 6, 2022
1 parent 7053463 commit 16973e2
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions 07-routing-gossip.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 16973e2

Please sign in to comment.