mirrors/lightning-bolts
1
0
Fork 0
mirror of https://github.com/lightning/bolts.git synced 2025-03-10 09:10:07 +01:00
Code Issues Projects Releases Wiki Activity

Clarify the semantics of max_htlc_value_in_flight_msat

Browse source 
Prior wording of the description of this parameter left room for
ambiguity around whether it capped the total value offered by both
channel peers combined or if it was solely capping the total value
of HTLCs offered by the remote.
This commit is contained in:
Keagan McClelland 2023-09-20 15:03:59 -07:00 • committed by Rusty Russell
parent 6649f51228
commit 4dcc377209
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
02-peer-protocol.md
View file

@ -157,9 +157,9 @@ payment. `htlc_minimum_msat` indicates the smallest value HTLC this
node will accept.
`max_htlc_value_in_flight_msat` is a cap on total value of outstanding
HTLCs, which allows a node to limit its exposure to HTLCs; similarly,
`max_accepted_htlcs` limits the number of outstanding HTLCs the other
node can offer.
HTLCs offered by the remote node, which allows the local node to limit its
exposure to HTLCs; similarly, `max_accepted_htlcs` limits the number of
outstanding HTLCs the remote node can offer.
`feerate_per_kw` indicates the initial fee rate in satoshi per 1000-weight
(i.e. 1/4 the more normally-used 'satoshi per 1000 vbytes') that this
@ -1071,7 +1071,7 @@ A sending node:
- if result would be offering more than the remote's
`max_accepted_htlcs` HTLCs, in the remote commitment transaction:
- MUST NOT add an HTLC.
- if the sum of total offered HTLCs would exceed the remote's
- if the total value of offered HTLCs would exceed the remote's
`max_htlc_value_in_flight_msat`:
- MUST NOT add an HTLC.
- for the first HTLC it offers: