-
Notifications
You must be signed in to change notification settings - Fork 18
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
Failure messages #166
base: master
Are you sure you want to change the base?
Failure messages #166
Conversation
cb7e8f1
to
43b2c52
Compare
43b2c52
to
9e523f9
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, but I don't know if it's a good idea to use it in prod before lightningnetwork/lnd#7067 is merged
Put on hold until lightningnetwork/lnd#7067 is merged. |
Instead of failure codes, we use failure messages. This gives lspd more control over the returned failure to the sender. In the case of a temporary channel failure for example, we are able to return the correct channel policy in the failure message, so the sender may be able to retry. This also allows us to return any error code, and aligns the interfaces for cln and lnd.
** !! **
Requires an update to LND, to include this PR lightningnetwork/lnd#7067
It is included in lnd here https://github.com/breez/lnd/tree/unencrypted-failure-messages