Add ProbingService: optional service for periodic probe payments
#678
Conversation
…valuate channel liquidity and identify reliable routes - Allows clients to configure probing interval, max targets, and probe amount in sats - Targets peers with highest capacity for sending small, intentional payment failures - Non-mandatory feature to enhance routing decisions via network probing
|
👋 Thanks for assigning @tnull as a reviewer! |
|
🔔 1st Reminder Hey @tnull! This PR has been waiting for your review. |
|
🔔 2nd Reminder Hey @tnull! This PR has been waiting for your review. |
There was a problem hiding this comment.
Thanks for looking into this!
Hmm, I think it makes sense to start out with a very simple strategy, but we should set this up to be more generic so that the ProbingService can handle a variety of different strategies going forward, ie., for example by adding a trait ProbingStrategy that the different strategies can implement. Such trait could have a simple fn next_target(probing_params: ProbingParameters) -> PublicKey method or similar.
3 participants
Add
ProbingService, an optional background service that periodically sends probe payments to selected network targets.Users can enable it when building the node and configure interval, target count, and probe amount.
It helps collect routing data and improve scoring reliability, following the idea of running LDK nodes as background probers.