Reduce default max_channel_saturation_power_of_half to 2 (max 1/4) 2022-07-no-rand-path-selection
authorMatt Corallo <git@bluematt.me>
Tue, 12 Jul 2022 21:13:30 +0000 (21:13 +0000)
committerMatt Corallo <git@bluematt.me>
Tue, 19 Jul 2022 15:16:35 +0000 (15:16 +0000)
commitff8d3f7ba454b957a22f80f2ccb1dcef81e470e5
tree09c5bd0c5ffe9c7a35ec57a8c4aa960f75bf378b
parent985153e1284c9314f417d614a6a5de7e796c6ef7
Reduce default max_channel_saturation_power_of_half to 2 (max 1/4)

Saturating a channel beyond 1/4 of its capacity seems like a more
reasonable threshold for avoiding a path than 1/2, especially given
we should still be willing to send a payment with a lower
saturation limit if it comes to that.

This requires an (obvious) change to some router tests, but also
requires a change to the `fake_network_test`, opting to simply
remove some over-limit test code there - `fake_network_test` was
our first ever functional test, and while it worked great to ensure
LDK worked at all on day one, we now have a rather large breadth
of functional tests, and a broad "does it work at all" test is no
longer all that useful.
lightning/src/ln/functional_tests.rs
lightning/src/routing/router.rs