]> git.bitcoin.ninja Git - rust-lightning/commit
Don't interpret decayed data as we've failed to send tiny values 2024-10-decayed-non-null
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 19:38:16 +0000 (19:38 +0000)
commit41a91a395a1500b2529a839a25f6d7de035bbe44
treef17aa81e9caf564d82e326283ab89cddd82b2e3d
parent46d8a0db79f3257cd5f2a6cdf896b1577ffccd88
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