Expose LSPS1 channel-purchase APIs #312

Activity

1. yahia008 commented on Nov 2, 2026

   

   yahia008

   on Nov 2, 2026

   More actions

   Hi, I'd like to work on this one.

   I looked at the pinned ldk-node rev (179b4b2). The two calls to expose are
   LSPS1Liquidity::request_channel and check_order_status, both returning an
   LSPS1OrderStatus (order params, payment options for BOLT11/BOLT12/on-chain, and channel
   info once funded).

   To keep the review small, I'll split this into two PRs:

   1. check_order_status, the read-only call
   2. request_channel, which places the order, stacked on top of the first

   Each one follows CONTRIBUTING and uses #324 as the template (proto, handler, route,
   permission, client, CLI, MCP tool, docs and tests). Permissions, unless you'd prefer
   otherwise: channels:read for the status check and channels:manage for requesting a
   channel, like OpenChannel and splicing.

   I'll start on the first PR now. If you'd prefer a different permission mapping or a single
   PR, just say so and I'll adjust.
2. Anyitechs commented on Nov 2, 2026

   

   Anyitechs

   on Nov 2, 2026

   Contributor

   More actions

   Hey @elnafateh @yahia008. Thank you for showing interest in this, but we can't expose this yet as there's no service support for LSPS1 yet in LDK-Node. I already started that integration here and will downstream the full LSPS1 support to LDK-Server once that lands in LDK-Node.