# Time-Weighted Delegation Power **URL:** \ **Category:** Temperature Check\ **Created:** [August 21, 2023, 1:32am UTC](https://forum.sundaeswap.finance/t/time-weighted-delegation-power/3182 "2023-08-21T01:32:16Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![Serotonin](https://avatars.discourse-cdn.com/v4/letter/s/c37758/32.png) [@Serotonin](https://forum.sundaeswap.finance/u/Serotonin)\ **Post date:** [August 21, 2023, 9:10pm UTC](https://forum.sundaeswap.finance/t/time-weighted-delegation-power/3182/7 "2023-08-21T21:10:37Z")
Ahh, I did not realize that an update to _any_ LP position would result in resetting the timer. Yes, this changes the situation quite a bit. > Instead, I think a far more elegant solution that avoids all of this is: > > - when computing delegation amounts to each pool > - first compute the midnight snapshot as normal > - then, add up the last N days worth of delegation by pool 😆 That was my original suggestion [(option 1)](https://forum.sundaeswap.finance/t/smoothing-delegation-volatility/3175/2), but I thought that you had mentioned in discord that the time weighted average would somehow actually be easier to implement than an N-day simple moving average. With this understanding, I’d rather put forward a temperature check with the N-day simple moving average. Having your delegation reset when “topping off” your Sundae delegation might have been a reasonable sacrifice in the short-term to get something quickly deployed if it meant the work would also contribute towards a longer term solution using the time-weighted average. But if it means that redistributing liquidity to any LP pool resets the clock, then that is _not_ a reasonable tradeoff imo (and wouldn’t really address the HRA “inconsistency” as well as leading to “unintentional” masking of delegation power) --- _[View the full topic](https://forum.sundaeswap.finance/t/time-weighted-delegation-power/3182)._