Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use LocalHTLCFailureReason in Onion Processing #3744
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
base: main
Are you sure you want to change the base?
Use LocalHTLCFailureReason in Onion Processing #3744
Changes from all commits
29f0ccb
728ab01
54f18b8
2cc8799
7c78b01
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
In
decode_incoming_update_add_htlc_onion
,encode_malformed_error
could have itsmessage
param dropped perhaps.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.
We lose some information from the
encode_relay_error
calls eg: "Underflow calculating outbound amount or cltv value for blinded forward" just turns intoInvalidOnionBlinding
.Tension between internal/api struct shows up there.
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.
Doesn't that indicate that another enum value is needed, that is mapped to InvalidOnionBlinding on the wire?
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.
We could add that, but IMO it's not interesting to surface that on the API, and they all map to the same bolt04 code.
So we'd be adding a new enum variant just for the sake of getting rid of a string - not worth the change IMO.
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.
It isn't completely clear to me why something like
Underflow calculating outbound amount or cltv value for blinded forward
isn't interesting to surface on the API, while other internal reasons that are also not uniquely mapped to a bolt code are.This particular string also occurs in the code base multiple times.
But fine to leave as is.