LDK Node v0.2 Tracking Issue #107

Activity

1. tnull

   added this to the 0.2 milestone on May 22, 2023
2. tnull

   added this to LDK Prioritieson May 22, 2023
3. tnull

   self-assigned this

   on May 22, 2023
4. tnull

   moved this to In Progress in LDK Prioritieson May 22, 2023
5. ariard commented on May 23, 2023

   

   ariard

   on May 23, 2023

   More actions

   We can add #98 as a v0.2 target ? Interested to collect more feedbacks from the LDK ecosystem at large.
6. tnull commented on May 23, 2023

   

   tnull

   on May 23, 2023

   CollaboratorAuthor

   More actions

   We can add #98 as a v0.2 target ? Interested to collect more feedbacks from the LDK ecosystem at large.

   I don't think so as this issue is meant to be a (short-term) tracking issue for the 0.2 release, while #98 seems like a much longer term project, most of which probably will live outside this repository (namely, any binary/daemon).
7. ariard commented on May 23, 2023

   

   ariard

   on May 23, 2023

   More actions

   I don't think so as this issue is meant to be a (short-term) tracking issue for the 0.2 release, while #98 seems like a much longer term project, most of which probably will live outside this repository (namely, any binary/daemon).

   Okay I'll see to build on top of ldk-node as this is already a huge simplification of our base API and move a binary/daemon in its own repository. If we spend time on communication cost over engineering time it's not worthy to share the maintenance cost.
8. tnull

   closed this as completedon Dec 13, 2023
9. github-project-automation

   moved this from In Progress to Done in LDK Prioritieson Dec 13, 2023
10. joostjager

    added a commit that references this issue on Jan 28, 2026

    Merge pull request lightningdevkit#107 from joostjager/connect-peer

    a3f3678