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

s/send a warning/warn the user/ in BOLT 5 to avoid confusion (#951)

Browse Source 
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.
This commit is contained in:
Matt Corallo 2022-01-17 18:40:47 +00:00 committed by GitHub
parent ea37941537
commit c878cd8e1d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
05-onchain.md
View File

@ -361,7 +361,7 @@ A local node:
- MUST handle HTLCs offered by the remote node as specified in - 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) [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): - 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 ## Rationale
@ -625,7 +625,7 @@ A node:
- upon discovering a transaction that spends a funding transaction output - upon discovering a transaction that spends a funding transaction output
which does not fall into one of the above categories (mutual close, unilateral which does not fall into one of the above categories (mutual close, unilateral
close, or revoked transaction close): 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 - 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. 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. - MAY simply monitor the contents of the most-work chain for transactions.