SpikeSwap
- Completed
-
Audit Report
Commissioned
23 Dec 2021
Completed
07 Jan 2022
Contracts Audited
ySpikeToken 0x9145BDFeb48e0B5d1B649EED068E80f209889f6d MasterChef 0x0d6BD191CFEA27e3B6375Fdc12248d9769b5B61C Referral 0xc9B32f92390548D4A6d6A222eb9fb4E044E9E481 Timelock 0x0A20A8c297D058B34610E15a0B33af35CD8F2afe View Audit Report
IssuesRisk SummaryFound Resolved Partially Resolved Acknowledged
(no change made)High 4 4 – – Medium 3 3 – – Low 9 7 – 2 Informational 9 3 – 6 Total 25 17 – 8 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.