Skip to content

Support Splicing in LSPS2 #763

Open
Open

Description

@TheBlueMatt

We shouldn't open a new channel with a client if we already have one. This may be a simple doc + ldk-node update, or there could be more, not sure.

Activity

  1. added this to the 0.4 milestone on Jan 20, 2026
  2. tnull commented on Jan 21, 2026

    @tnull
    Collaborator

    This may be a simple doc + ldk-node update, or there could be more, not sure.

    It is, especially since anything beyond just using splicing when you'd usually use a new channel wouldn't work out, cf the discussion over at lightning/blips#65. I'm going ahead and move this issue over to LDK Node.

  3. removed this from the 0.4 milestone on Jan 21, 2026
  4. Jolah1 commented on Apr 22, 2026

    @Jolah1
    Contributor

    I'd like to work on this.

    My approach is to check for an existing channel with their_network_key in the OpenChannel service event handler, and splice into it instead of opening a new one when one exists.

    I'll also update the LSPS2ServiceConfig docs to reflect the new behavior.

  5. tnull commented on Apr 22, 2026

    @tnull
    Collaborator

    No, unfortunately this is currently still blocked on the bLIPs PR linked above, which I will take over soon to make some progress there.

  6. Jolah1 commented on Apr 22, 2026

    @Jolah1
    Contributor

    Alright then!

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions