Spooky
- Completed
-
Audit Report
Commissioned
15 Jul 2022
Completed
28 Aug 2022
Contracts Audited
MasterChefV2 0x9C9C920E51778c4ABF727b8Bb223e78132F00aA4 ChildRewarder N/A ComplexRewarder 0xDdB816c59200aF55b1Ca20735Ef086626a2C6a8D LiquidityBrewer 0xBD3F7692B0b907735b0feBd9b82d39c3C5Bf2E99 SpookyAuth Dependency of LiquidityBrewer Multicall Dependency of LiquidityBrewer SelfPermit Dependency of LiquidityBrewer FarmController N/A View Audit Report
IssuesRisk SummaryFound Resolved Partially Resolved Acknowledged
(no change made)High 0 – – – Medium 3 0 – 3 Low 7 2 – 5 Informational 29 6 1 22 Total 39 8 1 30 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.