The strategy's _harvestAndReport() function lacks implementation of the shutdown check mechanism that is standard in Yearn V3 protocols. While the function is permissioned, the absence of this safety control would impact the protocol's ability to properly handle emergency situations.
The current implementation of `_harvestAndReport()`:
The function only performs balance checks without:
Implementing the shutdown state check
Having active management logic for rewards/redeployment
Including emergency withdrawal capabilities
this function is permissioned and can only be called by trusted addresses, but it deviates from the Yearn V3 standard implementation which includes critical safety controls.
while the Yean 3 implementation specifics
Limited control during emergency scenarios
No distinction between normal operation and shutdown states
Potential inefficiencies in capital deployment
Missing opportunity to implement emergency fund-securing mechanisms
Manual code review
Comparison with Yearn V3 implementation
https://docs.yearn.fi/developers/v3/strategy_writing_guide
Implement the standard shutdown check pattern with active management:
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.