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

BOLT 5: fix requested changes by @rustyrussell

Browse source
This commit is contained in:
Landon Mutch 2017-12-14 10:31:15 -08:00 • committed by Rusty Russell
parent 1a2021ea91
commit bd1fc7dfef
1 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
05-onchain.md
View file

@ -111,7 +111,7 @@ for more details.
# Failing a Channel # Failing a Channel
Although, closing a channel can be accomplished in several ways, the most Although closing a channel can be accomplished in several ways, the most
efficient is preferred. efficient is preferred.
Various error cases involve closing a channel. The requirements for sending Various error cases involve closing a channel. The requirements for sending
@ -188,10 +188,10 @@ A node:
- MAY ignore the `to_remote` output. - MAY ignore the `to_remote` output.
- Note: No action is required by the local node, as `to_remote` is - Note: No action is required by the local node, as `to_remote` is
considered *resolved* by the commitment transaction itself. considered *resolved* by the commitment transaction itself.
- [FIXME: SHOULD|MAY|MUST?] handle HTLCs offered by itself as specified in - MUST handle HTLCs offered by itself as specified in
"HTLC Output Handling: Local Commitment, Local Offers" below. [HTLC Output Handling: Local Commitment, Local Offers](#htlc-output-handling-local-commitment-local-offers).
- [FIXME: SHOULD|MAY|MUST?] handle HTLCs offered by the remote node as - MUST handle HTLCs offered by the remote node as
specified in "HTLC Output Handling: Local Commitment, Remote Offers" below. specified in [HTLC Output Handling: Local Commitment, Remote Offers](#htlc-output-handling-local-commitment-remote-offers).
## Rationale ## Rationale
@ -536,7 +536,7 @@ transaction.
With a maximum standard weight of 400000, the maximum number of HTLCs that can With a maximum standard weight of 400000, the maximum number of HTLCs that can
be swept in a single transaction: be swept in a single transaction:
max_num_htlcs = [400000 - 324 - 272 - (4 * 53) - 2] / 413 = 966 max_num_htlcs = (400000 - 324 - 272 - (4 * 53) - 2) / 413 = 966
This allows 483 HTLCs in each direction (with both `to_local` and This allows 483 HTLCs in each direction (with both `to_local` and
`to_remote` outputs) to still be resolved in a single penalty transaction. `to_remote` outputs) to still be resolved in a single penalty transaction.