Skip to content

Commit

Permalink
Clarify a few requirements
Browse files Browse the repository at this point in the history
As suggested by @yyforyongyu.
  • Loading branch information
t-bast committed Jan 27, 2025
1 parent 858b4d9 commit 922b61f
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion 02-peer-protocol.md
Original file line number Diff line number Diff line change
Expand Up @@ -1868,7 +1868,7 @@ The sender of `closing_complete` (aka. "the closer"):
- If it does, the output value MUST be set to zero so that all funds go to fees, as specified in [BOLT #3](03-transactions.md#closing-transaction).
- If the closee's output amount is dust:
- MUST set `closer_output_only`.
- SHOULD NOT set `closer_and_closee_outputs`.
- MUST NOT set `closer_and_closee_outputs`.
- Otherwise:
- MUST set both `closer_output_only` and `closer_and_closee_outputs`.
- MUST generate its closing transaction as specified in [BOLT #3](03-transactions.md#closing-transaction).
Expand All @@ -1887,6 +1887,10 @@ The receiver of `closing_complete` (aka. "the closee"):
- SHOULD ignore `closing_complete`.
- SHOULD send a `warning`.
- SHOULD close the connection.
- If `closer_scriptpubkey` is invalid (as detailed in the [`shutdown` requirements](#closing-initiation-shutdown)):
- SHOULD ignore `closing_complete`.
- SHOULD send a `warning`.
- SHOULD close the connection.
- If `closer_scriptpubkey` is a valid `OP_RETURN` script:
- MUST set its output amount to zero so that all funds go to fees, as specified in [BOLT #3](03-transactions.md#closing-transaction).
- MUST generate the remote closing transaction as specified in [BOLT #3](03-transactions.md#closing-transaction).
Expand Down

0 comments on commit 922b61f

Please sign in to comment.