matt on Nostr: The issues raised by lipa in their post (that LDK is a complicated API and a lot to ...
The issues raised by lipa in their post (that LDK is a complicated API and a lot to work with, that RGS had some stability issues, and that LDK’s pathfinding was sub-optimal) are things that were true a year ago, but are also things that have been largely addressed by LDK itself since -
The introduction of ldk-node has made it incredibly easy to get from zero to a full lightning node on a phone in minutes, RGS has seen a lot of debugging and improvements, and LDK’s pathfinding is now by far the most advanced in lightning (but, like with all lightning nodes, you need to be well connected or have sent a lot of payments to have data to use for pathfinding).
The introduction of ldk-node has made it incredibly easy to get from zero to a full lightning node on a phone in minutes, RGS has seen a lot of debugging and improvements, and LDK’s pathfinding is now by far the most advanced in lightning (but, like with all lightning nodes, you need to be well connected or have sent a lot of payments to have data to use for pathfinding).
quoting note1zsm…a33wA great write up about LDK challenges and why they moved to Breez. All of these we also ran into and solved:
1. Custom rust library around LDK
1. Rapid Gossip Sync bugs and slow syncing
2. Unreliable routing algorithm
3. Concurrent device access w/ just seed word backup
If you would like advice building on LDK or would like to use our MIT libraries to assist in the development of your wallet, please reach out.
We're a small team of 3 people but happy to help in any way we can.
https://medium.com/@lipa_btc/navigating-lightning-innovation-lipas-journey-from-ldk-to-breez-sdk-c5ba36550000