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
We had users interested in circular rebalancing. Of course, selecting two channels (send/receive over) to use, crafting an appropriate path and sending a spontaneous payment should be rather trivial to achieve with LDK's current API, but it would still be nice to have a convenient helper method for it, similar as we do for payment probing.
Yeah, that might be a prereq, but I think this issue is slightly different, as it's about providing convenience helpers to create a circular route mostly.
I believe #2462 is unrelated. #2462 is about detecting when a payment is to-self and short-circuiting the actual HTLC logic. This is somewhat of the opposite - using the normal HTLC logic for a self-payment anyway.
I believe #2462 is unrelated. #2462 is about detecting when a payment is to-self and short-circuiting the actual HTLC logic. This is somewhat of the opposite - using the normal HTLC logic for a self-payment anyway.
Well, in both cases we'll have to deal with the case where the destination / route's last hop is our own node. The only difference is the length of the circle. I agree it's a bit orthogonal, but at the very least we'll need to make sure that the short-circuiting for the 0-hop case is done in a way that still allows us to send payments across circular paths with >0 length.
Activity
valentinewallace commentedon May 22, 2025
May be a duplicate of #2462
tnull commentedon May 23, 2025
Yeah, that might be a prereq, but I think this issue is slightly different, as it's about providing convenience helpers to create a circular route mostly.
ouchennnn commentedon May 31, 2025
hi can I take this ?
tnull commentedon Jun 2, 2025
Yes, although we might need #2462 first, as discussed above. Would you also be interested in picking that up?
ouchennnn commentedon Jun 2, 2025
yes sure 🙂
TheBlueMatt commentedon Jul 16, 2025
I believe #2462 is unrelated. #2462 is about detecting when a payment is to-self and short-circuiting the actual HTLC logic. This is somewhat of the opposite - using the normal HTLC logic for a self-payment anyway.
tnull commentedon Jul 17, 2025
Well, in both cases we'll have to deal with the case where the destination / route's last hop is our own node. The only difference is the length of the circle. I agree it's a bit orthogonal, but at the very least we'll need to make sure that the short-circuiting for the 0-hop case is done in a way that still allows us to send payments across circular paths with >0 length.
TheBlueMatt commentedon Jul 18, 2025
Sure, indeed, but no reason we can't make progress on this issue while work goes on there.
Thrishalmadasu commentedon Feb 3, 2026
Can I pick this up?
TheBlueMatt commentedon Feb 3, 2026
Sure!
Ferryx349 commentedon May 10, 2026
Can i work on this?
Ferryx349 commentedon May 10, 2026
@Thrishalmadasu are u still working on this??
Thrishalmadasu commentedon May 10, 2026
@Ferryx349 you can pick it up