Skip to content

Commit

Permalink
s/send a warning/warn the user/ in BOLT 5 to avoid confusion (#951)
Browse files Browse the repository at this point in the history
Prior to the addition of `warning` messages, BOLT 5 specified a
few cases where users should be warned that funds may have been
lost. However, it used the phrasing "send a warning" which can now
be confused  with `warning` messages. Nodes should not generally
inform their counterparty that they have been robbed.
  • Loading branch information
TheBlueMatt authored Jan 17, 2022
1 parent ea37941 commit c878cd8
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions 05-onchain.md
Original file line number Diff line number Diff line change
Expand Up @@ -361,7 +361,7 @@ A local node:
- MUST handle HTLCs offered by the remote node as specified in
[HTLC Output Handling: Remote Commitment, Remote Offers](#htlc-output-handling-remote-commitment-remote-offers)
- otherwise (it is NOT able to handle the broadcast for some reason):
- MUST send a warning regarding lost funds.
- MUST inform the user of potentially lost funds.

## Rationale

Expand Down Expand Up @@ -625,7 +625,7 @@ A node:
- upon discovering a transaction that spends a funding transaction output
which does not fall into one of the above categories (mutual close, unilateral
close, or revoked transaction close):
- MUST send a warning regarding lost funds.
- MUST warn the user of potentially lost funds.
- Note: the existence of such a rogue transaction implies that its private
key has leaked and that its funds may be lost as a result.
- MAY simply monitor the contents of the most-work chain for transactions.
Expand Down

0 comments on commit c878cd8

Please sign in to comment.