-
Notifications
You must be signed in to change notification settings - Fork 371
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
Include counterparty node ids in PaymentForwarded #3458
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3458 +/- ##
==========================================
+ Coverage 89.69% 89.86% +0.16%
==========================================
Files 130 130
Lines 107422 108677 +1255
Branches 107422 108677 +1255
==========================================
+ Hits 96354 97661 +1307
+ Misses 8672 8640 -32
+ Partials 2396 2376 -20 ☔ View full report in Codecov by Sentry. |
3ec8edf
to
69f3136
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, modulo one tiny nit.
This commit adds counterparty node IDs to `PaymentForwarded` to address the potential ambiguity of using `ChannelIds` alone, especially in cases like v1 0conf opens where `ChannelIds` may not be unique. Including the counterparty node IDs provides better clarity and makes the information more useful.
Updated from pr3458.02 to pr3458.03 (diff): Changes:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Wow, so fast! Thanks everyone! |
resolves #3455
This commit adds counterparty node IDs to
PaymentForwarded
to address the potential ambiguity of usingChannelIds
alone, especially in cases like v1 0conf opens whereChannelIds
may not be unique. Including the counterparty node IDs provides better clarity and makes the information more useful.