Skip to content

Beta Release #121

Description

@benthecarman

Activity

  1. benthecarman commented on Feb 6, 2026

    @benthecarman
    CollaboratorAuthor

    Stretch goals / longer term:

    • LSPS 5 support
    • Channel rebalancing tooling (circular rebalances)
    • Look into potentially switching to gRPC
    • LSPS "risk analysis": Force-close cost estimation, offline channels, etc
  2. toneloc commented on Feb 23, 2026

    @toneloc

    What's the ETA on the beta release? Thank you for your work.

  3. benthecarman commented on Feb 23, 2026

    @benthecarman
    CollaboratorAuthor

    Hoping by the end of Q1

  4. toneloc commented on Feb 23, 2026

    @toneloc

    Nice I'll be ready to test! When ready, I am also interested in some Mutintynet or Testnets going on where we can test stuff.

  5. HARSHVARANDANI commented on May 16, 2026

    @HARSHVARANDANI
    Contributor

    Hey @benthecarman is there anything I can take up from these? I see there are PRs open for most of these if there's anything I can take up that'd be great.

  6. benthecarman commented on May 16, 2026

    @benthecarman
    CollaboratorAuthor

    @HARSHVARANDANI most of the work for ldk-server is actually is in ldk-node. I would look through there

  7. f3r10 commented on Sep 21, 2026

    @f3r10
    Contributor

    I'd like to help with the beta release if there's anything open I could pick up. @benthecarman

    Looking at the list, most items seem to be moving: forwarding history landed with #283 and Postgres with #243. The one that stands out to me is "Accounting / profitability tooling" under LSP Utilities, since I couldn't find an issue or PR for it. Is that still wanted, and is anyone working on it?

    With #283 merged, most of the data seems to be there already: ListChannelForwardingStats has the fees earned and skimmed per channel, and ListPayments has the on-chain costs with tx_type and channel ids. What's missing is something that joins the two so an operator can see whether a channel is actually profitable. If that sounds right I'd be happy to open an issue with a concrete proposal and work on it.

    One small thing: "LSP events in rabbitmq publisher" looks obsolete now that #176 replaced RabbitMQ with gRPC, so that line could probably be dropped or reworded.

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