-
Notifications
You must be signed in to change notification settings - Fork 890
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
getting WIRE_EXPIRY_TOO_SOON #2208
Comments
Can you share a concrete example (route and error message returned by This caused by one of the nodes along the route not being given a sufficient CLTV delta. This can be cause by a number of issues:
I think it's most likely the first, but we'll need more information to confirm that. |
|
why "pay" command doest work in case nonadvertised nodes (channels)? giving "could not find a route" error. Is it related to: /* FIXME: use b11->routes */ in payalgo.c? |
Ok, so the issue is the I take it you are building these routes manually? @rustyrussell is working on a plugin version of the |
as i said i tryed different combinations of delay, 28->14, 14->9, 9->14, 128->9 and many others, all of them gives same error. Yes route is build manually based on r record from invoice. But is correct, destinantin node is connected to the same peer as my node, getroute gives common peer route info and destination channelid is in invoice. |
The intermediate node appears to be an |
i didnt try exactly 153 so should it be like that?: |
intermediate node is zigzag.io and oryginally on getroute returns delay=9 |
Could be that the fees do not match exactly in the route, but at least you'll get a different error 😉
|
yes, fees miss much gives different error. I will check delay values You mentioned and let You know. |
otherwise i have to jump into lnd and GOshit |
You said that @rustyrussell is working on plugin to handle nonannouced nodes pay transactions. Why it is solved as plugin and not in main code? |
The reason it is being done as a plugin is that the We will provide a sane default plugin, but clearly we also want to give users the ability to add their own logic, and give them the control they might want to have, hence the plugin which allows users to implement their own policies. |
Is this issue still relevant? |
Closing possibly-stale issue |
Issue and Steps to Reproduce
./lightnig-cli sendpay "$route" id
and getting WIRE_EXPIRY_TOO_SOON from one of the peers
what is causing the error?
getinfo
outputThe text was updated successfully, but these errors were encountered: