LDK Node v0.2 Tracking Issue

[tnull]

• Upgrade to LDK 0.0.116 (Upgrade to LDK 0.0.116 #105)
• Upgrade to LDK 0.0.117 (Upgrade to LDK 0.0.117 #151)
• Upgrade to LDK 0.0.118 (Upgrade to LDK 0.0.118 #175)
• Remember and sweep spendable outputs (Remember and regularly sweep spendable outputs #94)
• Figure out if we need to cache broadcasts, handle rebroadcasting (Figure out rebroadcasting / RBF strategy #22)
• Figure out if/how we need to expose more (e.g., Expose more ChannelDetails fields #90)
• Add python packaging (Add python packaging #128)
• Allow to check if node is running (Check if node is running #164)
• Fix peer info persistence for inbound channels (PeerInfo is not persisted if the channel is inbound #133)

[ariard]

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

[tnull]

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).

[ariard]

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.