Support LDK server (daemon node)#1
Conversation
Explores the addition of a client to manage communication with an instance of an ldk-server. We realize early the disparity between the local node information APIs exposed by LDK, relative to LND and CLN, and need to add feature support on ldk-node/server to permit the retrieval of the running node's network and features. These are necessary for sim-ln's validation logic as: - network ensures all nodes run on the same network, and also do not run on the mainnet - features ensure that keysend support is enabled
a6fcf00 to
e9abc14
Compare
|
The network field has been added to ldk-node: lightningdevkit/ldk-node#892 Also it seems for sim-ln we don't really need to have features exposed, as it only uses the basic functionality. Unfortunately I didn't see this PR draft before I explored open PRs to ldk-node, as it is a draft in your own fork. |
Thanks for doing this. I've been working on other things and this slipped down the order.
It's fine. I'll close this and review yours as you already have the PR up. |
What this PR does
Exploratory PR to support LDK server, i.e. LDK node daemon, as one of
sim-ln's node targets.As efforts progress and required LDK-dependent feature set identified, corresponding PRs will
be opened on
ldk-node/serverto enable integration.Required LDK feature set*
To integrate
sim-ln:ldk-node, we need to enable, or make accessible, the following:networkavailable in request to get node informationNodeFeaturesavailable in request to get node information*Will be modified as new features are discovered