evoDefi (AMM on HSC)
- Completed
-
Audit Report
Commissioned
28 Aug 2021
Completed
30 Aug 2021
Contracts Audited
EvoSwapV2Router 0x9a45723AA0F705B1DCf9bd8C2099d3663fB967f9 EvoSwapV2Factory 0x3bab5FA55CD0E476006f3850A5e8E173D7Bbb166 EvoSwapV2Pair Created by factory or router: check creation transaction to verify that the pair was created by the factory EvoSwapV2ERC20 Dependency EvoSwapV2Library Dependency View Audit Report
IssuesRisk SummaryFound Resolved Partially Resolved Acknowledged
(no change made)High
0 – – – Medium
0 – – – Low
1 – – 1 Informational
4 – – 4 Total 5 – – 5 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.