
YieldWolf
- Completed
-
Audit Report
Commissioned
15 Sep 2021
Completed
24 Sep 2021
Contracts Audited
YieldWolf 0xbf65023bcf48ad0ab5537ea39c9242de499386c9 AutoCompoundStrategy Inherited by ACMasterChef ACMiniChef 0x250B171274beFa912C0993FB037705920bB5147b ACMasterChefWithStaking 0x7De84ee43c4f7bA0487B77cD5Dd6f2D15903b33d ACMasterChefWithRef ACMasterChefWithRef.sol ACMasterChef 0x6D879b9c3B85F2Fe42e29318bdFA15055c6FA787 NativeValueLowerThanCondition Will not use in production SimpleWithdrawAction SimpleWithdrawAction.sol The client has said that would deploy ACMasterChefWithRef when they need to integrate a farm that requires this interface, and that SimpleWithdrawAction is meant to be deployed by users to use rules. For reference, the files that we have audited can be found in this GitHub commit.
View Audit Report
IssuesRisk SummaryFound Resolved Partially Resolved Acknowledged
(no change made)High
7 7 – – Medium
4 4 – – Low
8 7 – 1 Informational
9 7 – 2 Total 28 25 – 3 When using this protocol, the main risks you want to look out for are:
- Ensuring that the contracts you are interacting with matches the one we audited. This can be done by comparing the addresses with the one present in the contracts page in our audit.
- Our audits only cover code-related risks. Users will have to do their own due diligence on other aspects of the protocol such as the reputation of the team, the protocol’s tokenomics, and other aspects of the project that might be relevant.