]> git.bitcoin.ninja Git - rust-lightning/commit
Don't interpret decayed data as we've failed to send tiny values
authorMatt Corallo <git@bluematt.me>
Mon, 14 Oct 2024 17:11:04 +0000 (17:11 +0000)
committerMatt Corallo <git@bluematt.me>
Mon, 14 Oct 2024 17:28:36 +0000 (17:28 +0000)
commite48074afc9e600367694551e20b60457b0ba56f0
tree0278050be583351ce1c9e278850935292056ad78
parenta675d48cd4bb2c697ffb3be3c9f6103dd5ded5f1
Don't interpret decayed data as we've failed to send tiny values

When we're calculating the success probability for min-/max-bucket
pairs and are looking at the 0th' min-bucket, we only look at the
highest max-bucket to decide the success probability. We ignore
max-buckets which have a value below `BUCKET_FIXED_POINT_ONE` to
only consider values which aren't substantially decayed.

However, if all of our data is substantially decayed, this filter
causes us to conclude that the highest max-bucket is bucket zero
even though we really should then be looking at any bucket.

We make this change here, looking at the highest non-zero
max-bucket if no max-buckets have a value above
`BUCKET_FIXED_POINT_ONE`.
lightning/src/routing/scoring.rs