-
Notifications
You must be signed in to change notification settings - Fork 913
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
Renepay WIRE_INCORRECT_CLTV_EXPIRY #6620
Comments
Also, I think logs with sat amounts would be more readable, e.g. |
It's not bad for your funds' safety, but it is bad in terms of getting a payment through. It sounds like we either have a channel that recently changed its CLTV delta (time to take an upstream HTLC resolution, turn around and settle the downstream HTLC), or we are picking a wrong value from our local view (stale value, uninitialized value, ...). The good news is that the values are rather constrained due to what nodes will accept. If it is a node updating their delta, then we should be seeing this from time to time and see the update propagating through the network (they should technically accept the old value for a while until the network has seen the new value exactly to prevent this kind of issue). Let's monitor the situation and see if it happens and if we can see an update changing the value that we can correlate :-) |
Hmm, we apply the channel_update it sent (and it did send one, since you'd see a complaint here if we didn't). So let's assume renepay is getting it wrong, we just have to figure out how... |
1. When we add a shadow amount, we were using the wrong channel for the fee calculation. 2. Similarly, when calculating the delay amount. The result is that we can get WIRE_INCORRECT_CLTV_EXPIRY repeatedly from nodes. Reported-by: https://github.com/Sjors Fixes: ElementsProject#6620 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changlog-Experimental: Fixed: `renepay` handles ctlv correctly when it varies along a path.
Thanks @Sjors .... I hope you're keeping count of how many beers/equiv I owe you for such great bug reports! |
I'm not sure if
WIRE_INCORRECT_CLTV_EXPIRY
is perfectly normal or bad. #3862 suggests it's bad, so I figured I should open an issue.Using v28.08 I tried to make a 41623 sat payment.
Happy to send the uncensored log via email if needed.
I tried a regular
pay
a few minutes later which succeeded.The text was updated successfully, but these errors were encountered: