-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[bug]: lncli INCORRECT_OR_UNKNOWN_PAYMENT_DETAILS #8380
Comments
So it's by design that you will not receive a detailed error why the payment is not accepted, this helps against attacks. But because it is a rebalance payment as I see, you should see the reason in the logs of your node. Switch on the |
Thanks for the response. Can you elaborate on how to switch on the HSWC logging? Does that require setting debuglevel=debug and restarting or is there a hot way to enable it (or a different config way)? |
nevermind, I found it here:
trying now |
ok, great, so now I see:
Should I be setting a different flag somewhere in buildroute or addinvoice. Is this beacause the default expiry for addinvoice is 1 hour, but the first hop expiry is much longer? That Chan ID belongs to the middle node. It's unclear to me why the first hop got an expiry of |
This error sounds to me like one of the nodes isn't properly synced to the network and has a different block height than the others. |
Can you post the final_cltv_delta of the invoice and the blockheight your node is synced on, and try the payment again and post the error especially the failure blockheight ? |
My node is fully synced: 825901 (same as mempool.space shows) Invoice:
payment test again:
logs:
|
Your problem is the following: Your final_cltv_delta is 99 in the invoice. But buildroute uses 80 as a default so just use the custom final_ctlv_delta when building the route.
|
Normally lnd uses 80 as well, so I guess you are using the |
That worked perfectly! Thanks for all the help. Is this worth a more descriptive error message? |
Given that high fee environment docs encourage nodes to update |
A more explicit error message would need to be sent by the receiver of the payment. So a change in the spec would probably be required. Also, due to privacy reasons some errors are very vague on purpose. Therefore I don't think there's much to be done here. |
Agree, let's update the docs, I think that's the best we can do. |
Background
Using
buildroute
+sendtoroute
to construct a triangle and send funds through does not appear to work on lncli.Getting
INCORRECT_OR_UNKNOWN_PAYMENT_DETAILS
error without any other idea why the payment is not working.Full script, built path, and output below.
Your environment
lnd
Steps to reproduce
Expected behaviour
Payment succeeds or a more actionable error message informs what went wrong.
Actual behaviour
The text was updated successfully, but these errors were encountered: