Elk Finance
- Completed
-
Audit Report
Commissioned
18 Apr 2022
Completed
24 Apr 2022
Contracts Audited
Elk 0xeEeEEb57642040bE42185f49C52F7E9B38f8eeeE TeamVester TeamVester.sol ElkLabsVester ElkLabsVester.sol TokenVester TokenVester.sol Resolution https://github.com/elkfinance/governance/tree/ c3beac9b8a4b1d0caa57fe1de7678a66028c5afb/contracts The project team did not get back to us with the deployed addresses, so users should check that the code of the contract they are interacting with matches the code in the resolution GitHub commit.
View Audit Report
IssuesRisk SummaryFound Resolved Partially Resolved Acknowledged
(no change made)High 0 – – – Medium 0 – – – Low 2 2 – – Informational 11 9 – 2 Total 13 11 – 2 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.