Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Merged
merged 1 commit into from
Jan 17, 2022

Conversation

TheBlueMatt
Copy link
Collaborator

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.

Copy link
Collaborator

@t-bast t-bast left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch!

05-onchain.md Outdated Show resolved Hide resolved
Copy link

@freddiekrugerrand freddiekrugerrand left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fwiw bolt 1 also references a warning in "Also, on several platforms it's possible that Lightning
clients will be put to sleep without prior warning", but that's more clearly distinguished from the warning message imo so probably doesn't need changing.

Nice clarification!

Copy link
Contributor

@vincenzopalazzo vincenzopalazzo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, ACK fbee1da

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.
@TheBlueMatt TheBlueMatt force-pushed the 2022-01-warning-msg-confusion branch from fbee1da to 27e8d9d Compare January 17, 2022 17:03
@TheBlueMatt
Copy link
Collaborator Author

but that's more clearly distinguished from the warning message imo so probably doesn't need changing.

agreed, don't think its worth changing.

@cdecker
Copy link
Collaborator

cdecker commented Jan 17, 2022

ACK 27e8d9d

Copy link
Collaborator

@t-bast t-bast left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK 27e8d9d

@t-bast t-bast added the clarification substantive change or addition around wording or meaning label Jan 17, 2022
@t-bast t-bast merged commit c878cd8 into lightning:master Jan 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification substantive change or addition around wording or meaning
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants