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

BOLT 2: reduce HTLC maximum limit based on new penalty calculations.

Browse Source 
We can no longer allow 511 each way; reduce it to match our calculations
so we can always create a single standard penalty transaction.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
This commit is contained in:
Rusty Russell 2017-03-07 10:29:01 +10:30
parent 392008a7d3
commit 0d7cf77970
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
02-peer-protocol.md
View File

@ -143,7 +143,7 @@ unreasonably large. The receiver MAY fail the channel if
`funding-satoshis` is too small, and MUST fail the channel if `funding-satoshis` is too small, and MUST fail the channel if
`push-msat` is greater than `funding-amount` * 1000. `push-msat` is greater than `funding-amount` * 1000.
The receiving node MAY fail the channel if it considers The receiving node MAY fail the channel if it considers
`htlc-minimum-msat` too large, `max-htlc-value-in-flight` too small, `channel-reserve-satoshis` too large, or `max-accepted-htlcs` too small. It MUST fail the channel if `max-accepted-htlcs` is greater than 511. `htlc-minimum-msat` too large, `max-htlc-value-in-flight` too small, `channel-reserve-satoshis` too large, or `max-accepted-htlcs` too small. It MUST fail the channel if `max-accepted-htlcs` is greater than 483.
The receiver MUST fail the channel if it The receiver MUST fail the channel if it
considers `feerate-per-kw` too small for timely processing, or unreasonably large. The considers `feerate-per-kw` too small for timely processing, or unreasonably large. The
@ -590,7 +590,7 @@ Retransmissions of unacknowledged updates are explicitly allowed for
reconnection purposes; allowing them at other times simplifies the reconnection purposes; allowing them at other times simplifies the
recipient code, though strict checking may help debugging. recipient code, though strict checking may help debugging.
`max-accepted-htlcs` is limited to 511, to ensure that even if both `max-accepted-htlcs` is limited to 483, to ensure that even if both
sides send the maximum number of HTLCs, the `commit_sig` message will sides send the maximum number of HTLCs, the `commit_sig` message will
still be under the maximum message size. It also ensures that still be under the maximum message size. It also ensures that
a single penalty transaction can spend the entire commitment transaction, a single penalty transaction can spend the entire commitment transaction,