Skip to content

Add helper for circular rebalancing #3791

Open

Description

@tnull

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.

Activity

  1. valentinewallace commented on May 22, 2025

    @valentinewallace
    Contributor

    May be a duplicate of #2462

  2. tnull commented on May 23, 2025

    @tnull
    ContributorAuthor

    May be a duplicate of #2462

    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.

  3. ouchennnn commented on May 31, 2025

    @ouchennnn

    hi can I take this ?

  4. tnull commented on Jun 2, 2025

    @tnull
    ContributorAuthor

    hi can I take this ?

    Yes, although we might need #2462 first, as discussed above. Would you also be interested in picking that up?

  5. ouchennnn commented on Jun 2, 2025

    @ouchennnn

    yes sure 🙂

  6. TheBlueMatt commented on Jul 16, 2025

    @TheBlueMatt
    Collaborator

    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.

  7. tnull commented on Jul 17, 2025

    @tnull
    ContributorAuthor

    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.

  8. TheBlueMatt commented on Jul 18, 2025

    @TheBlueMatt
    Collaborator

    Sure, indeed, but no reason we can't make progress on this issue while work goes on there.

  9. Thrishalmadasu commented on Feb 3, 2026

    @Thrishalmadasu
    Contributor

    Can I pick this up?

  10. TheBlueMatt commented on Feb 3, 2026

    @TheBlueMatt
    Collaborator

    Sure!

  11. Ferryx349 commented on May 10, 2026

    @Ferryx349

    Can i work on this?

  12. Ferryx349 commented on May 10, 2026

    @Ferryx349

    @Thrishalmadasu are u still working on this??

  13. Thrishalmadasu commented on May 10, 2026

    @Thrishalmadasu
    Contributor

    @Ferryx349 you can pick it up

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions