You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we're doing pre-flight probing for a payment, and the last hop is from an invoice route hint, and there's only one option for the last-hop route, and the node is not public, there's no reason to probe through to the endpoint - we might as well probe to the second-to-last hop. Worse, probing to the endpoint may confuse some LSPs, causing them to open a JIT channel when there's no real payment yet. For ldk-node this should be ~easy, for LDK itself we probably want to do it as a part of #2499.
If we're doing pre-flight probing for a payment, and the last hop is from an invoice route hint, and there's only one option for the last-hop route, and the node is not public, there's no reason to probe through to the endpoint - we might as well probe to the second-to-last hop. Worse, probing to the endpoint may confuse some LSPs, causing them to open a JIT channel when there's no real payment yet. For ldk-node this should be ~easy, for LDK itself we probably want to do it as a part of #2499.
cc @tnull
The text was updated successfully, but these errors were encountered: