PolyFund
- Completed
-
Audit Report
Commissioned
31 Jul 2021
Completed
04 Aug 2021
Contracts Audited
FundToken 0x4b0f2da2c4e7cc60f3b918461ec4f16ccc974622 EmissionOracle 0xd31f67b07da248e0f68eabd110143a8a4537d2dd MasterChef 0xdA30Aae916417C9Ad8DE97Bb1d59395f2Dd905e4 PolyReferral 0xE42ce9eAC4b912471D724BCAd46A86Ae32D49082 SeedVault 0xdcfd912b50904B4d5745DfFe0D4d7a5097c82849 View Audit Report
IssuesRisk SummaryFound Resolved Partially Resolved Acknowledged
(no change made)High
4 3 – 1 Medium
5 1 – 4 Low
10 2 – 8 Informational
20 1 – 19 Total 39 7 – 32 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.