PolyShield
- Completed
-
Audit Report
Commissioned
09 Aug 2021
Completed
14 Aug 2021
Contracts Audited
MasterChef 0x0Ec74989E6f0014D269132267cd7c5B901303306 Polyshield (Token) 0xf239e69ce434c7fb408b05a0da416b14917d934e PolyshieldBurner 0xFbb307Fea8CdaF614B66f82D8d233c947B07c4F5 Timelock 0xa63C2e89441023DEC0258736531Da27af6230B19 View Audit Report
IssuesRisk SummaryFound Resolved Partially Resolved Acknowledged
(no change made)High 2 1 – 1 Medium 0 – – – Low 10 1 – 9 Informational 14 – – 14 Total 26 2 – 24 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.