Commit message · benthecarmanIncrease probabilistic scorer defaults 5x
Increase the base and historical-liquidity penalties fivefold. This
applies to both the fixed and payment-size parts, so their balance stays
the same. The router will now pay more to avoid longer routes and routes
the scorer considers less likely to work.
I tested this using the graph and scorer pulled from my ldk-server. The
scorer was kept unchanged during the test. Codex randomly assigned 600
different high-degree nodes to the old or new settings, with 300 probes
per setting. The test was balanced across 100 rounds and used amounts of
1,000, 10,000, and 30,000 sats. Only one probe ran at a time.
The old settings reached 167/300 targets (55.7%) within 10 seconds. The
5x settings reached 214/300 (71.3%), an improvement of 15.7 percentage
points. Results were 69% vs 82% at 1,000 sats, 47% vs 72% at 10,000
sats, and 51% vs 60% at 30,000 sats.
Across the 587 targets where both settings found a route, the quoted fee
rose by 2.4 sats on average. These probes used one node and did not
settle, so they do not guarantee payment success elsewhere.
90/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification
AI analysis · Informational 21/100This commit changes default numerical tuning knobs in the Lightning Dev Kit's payment router. It makes the router prefer shorter, more reliable payment paths by increasing several penalty values fivefold. The change is presented as a performance improvement (better routing success rates in tests), not as a security fix. There is no evidence in the commit of a vulnerability, exploit, or security incident.