mirrors/lightning-bolts
1
0
Fork 0
mirror of https://github.com/lightning/bolts.git synced 2024-11-19 01:50:03 +01:00
Code Issues Projects Releases Wiki Activity

BOLT 2: document requirements of max-htlc-value-in-flight-msat

Browse Source 
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
This commit is contained in:
Rusty Russell 2017-02-15 13:46:27 +10:30 committed by Pierre-Marie Padiou
parent a72b357ee6
commit f63d89c207
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
02-peer-protocol.md
View File

@ -581,7 +581,8 @@ the receiving node's `htlc-minimum-msat`.
A sending node MUST NOT add an HTLC if it would result in it offering
more than the remote's `max-accepted-htlcs` HTLCs in the remote commitment
transaction.
transaction, or if the sum of total offered HTLCs would exceed the remote's
`max-htlc-value-in-flight-msat`.
A sending node MUST set `id` to 0 for the first HTLC it offers, and
increase the value by 1 for each successive offer.
@ -591,7 +592,7 @@ A receiving node SHOULD fail the channel if it receives an
which the sending node cannot afford at the current `fee-rate` while
maintaining its channel reserve. A receiving node SHOULD fail the
channel if a sending node adds more than its `max-accepted-htlcs` HTLCs to
its local commitment transaction.
its local commitment transaction, or adds more than its `max-htlc-value-in-flight-msat` worth of offered HTLCs to its local commitment transaction.
A receiving node MUST allow multiple HTLCs with the same payment hash.