The updateUsageIndex function in the DebtToken contract is designed to be called by the LendingPool (ReservePool) to update the critical _usageIndex parameter. However, the LendingPool lacks a mechanism to invoke this function, resulting in an outdated _usageIndex.
This updateUsageIndex function update the _usageIndex that must be synchronized with the reserve.usageIndex in the lendingPool contract, While updateUsageIndex is protected by the onlyReservePool modifier, the LendingPool does not call this function.
The _usageIndex is intended to reflect real-time usage metrics (e.g., debt utilization). Without updates from the LendingPool, it becomes obsolete.
_usageIndex not synchronized with the reserve.usageIndex in the lendingPool contract. As a result, the value returned by getUsageIndex in DebtToken contract be outdated, leading to misaligned calculations.
Manual Review
Call DebtToken.updateUsageIndex(newValue) during key actions in the LendingPool that synchronized with the reserve.usageIndex.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.