PolySage
- Completed
-
Audit Report
Commissioned
04 Oct 2021
Completed
04 Oct 2021
Contracts Audited
SageToken 0x2ed945Dc703D85c80225d95ABDe41cdeE14e1992 MasterChef 0x0451b4893e4a77E7Eec3B25E816ed7FFeA1EBA68 Timelock 0xc8391D2ADF3969f2ecea18e69Af6Ca88abD452cb View Audit Report
IssuesRisk SummaryFound Resolved Partially Resolved Acknowledged
(no change made)High 0 – – – Medium 0 – – – Low 2 1 – 1 Informational 0 – – – Total 2 1 – 1 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.