Matt Corallo f0f8194719 Track historical liquidity update time separately from the bounds ... In the next commit, we'll start to use the new `ScoreUpdate::decay_liquidity_certainty` to decay our bounds in the background. This will result in the `last_updated` field getting updated regularly on decay, rather than only on update. While this isn't an issue for the regular liquidity bounds, it poses a problem for the historical liquidity buckets, which are decayed on a separate (and by default much longer) timer. If we didn't move to tracking their decays separately, we'd never let the `last_updated` field get old enough for the historical buckets to decay at all. Instead, here we introduce a new `Duration` in the `ChannelLiquidity` which tracks the last time the historical liquidity buckets were last updated. We initialize it to a copy of `last_updated` on deserialization if it is missing.		2023-12-13 23:26:09 +00:00
..
src	Track historical liquidity update time separately from the bounds	2023-12-13 23:26:09 +00:00
Cargo.toml	Depend on libm in no-std for powf(64)	2023-12-13 18:36:40 +00:00