The _harvestAndReport
function includes a comment suggesting that strategists should manually check the shutdown status using TokenizedStrategy.isShutdown()
. However, this check is not implemented within the function itself, which can lead to inconsistent behavior if not properly managed.
The function is designed to be called even post-shutdown, with the expectation that strategists will manage redeployment decisions based on the shutdown status. However, the absence of an internal check means this responsibility is left to external callers.
Without an internal check, the function may inadvertently redeploy funds during a shutdown, leading to operational inconsistencies and profits and losses could be inaccurately reported if the function continues normal operations during a shutdown.
Manual Review
Integrate a check for the strategy's shutdown status directly within the _harvestAndReport
function. This ensures consistent behavior regardless of external calls.
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.