Submitted by wagmi, also found by peritoflores, sces60107, __141345__, hansfriese, slowmoses, supernova, rvierdiiev, HollaDieWaldfee, and chaduke
When doing inflation, function getInflationAmt() calculated number of intervals elapsed by dividing the duration with interval length.
As we can noticed that, this calculation is rounding down, it means if block.timestamp - startTime = 1.99 intervals, it only account for 1 interval.
However, when updating start time after inflating, it still update to current timestamp while it should only increased by intervalLength * intervalsElapsed instead.
Since default value of inflation interval = 1 days and reward cycle length = 14 days, so the impact is reduced. However, these configs can be changed in the future.
Consider the scenario:
While at timestamp = 595, inflated times should be
(595 - 100) / 50 = 9 instead.
Consider only increasing InflationIntervalStartTime by the amount of intervals time interval length.
emersoncloud (GoGoPool) disagreed with severity and commented:
Alex the Entreprenerd (judge) decreased severity to Medium and commented:
emersoncloud (GoGoPool) commented:
