The deposit() and withdraw() functions in the LendingPool contract make redundant calls to updateReserveInterests().
When a user calls deposit() or withdraw(), the following sequence occurs:
The function first calls ReserveLibrary.updateReserveState(reserve, rateData), which internally calls updateReserveInterests() to update the reserve data.
After that, deposit() or withdraw() calls the corresponding function in ReserveLibrary.
However, inside ReserveLibrary.deposit() and ReserveLibrary.withdraw(), updateReserveInterests() is called again, making the first call redundant.
This results in unnecessary duplicate function calls, without adding any benefit.
Unnecessary computations, reducing efficiency. This issue does not cause any critical failures.
Remove one of the redundant calls to updateReserveInterests().
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.