Wiskers
- Completed
-
Audit Report
Commissioned
24 Sep 2023
Completed
05 Oct 2023
Contracts Audited
WiskersBase Dependency in WiskersUniswapV2Action WiskersUniswapV2Action 0x349752079EE6B7FB4f3Ca6B75c401bb0e65d2F83 WiskersToken 0xfD4Ca4a692f14d88af3E7Ae13Cf00D5095213B25 View Audit Report
IssuesRisk SummaryTH Found Resolved Partially Resolved Acknowledged
(no change made)High 2 2 – – Medium 4 1 – 3 Low 5 2 – 3 Informational 5 3 2 – Total 16 8 2 6 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.