Hexagon Finance
- Completed
-
Audit Report
Commissioned
02 Apr 2022
Completed
29 Apr 2022
Contracts Audited
MiniChefV2 MiniChefV2.sol lpGauge lpGauge.sol HexagonBoost HexagonBoost.sol hexagonBoostStorage hexagonBoostStorage.sol boostMultiRewarderTime boostMultiRewarderTime.sol VeFlake VeFlake.sol FlakeToken FlakeToken.sol Resolution https://github.com/HexagonFinance/hexagon-finance-farm/commit/2df6b2c8a6538ebae4df76865805dae006cb0083 The team did not get back to us with the deployed addresses for the other contracts, 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 7 5 1 1 Medium 7 5 – 2 Low 7 4 – 3 Informational 34 25 6 3 Total 55 39 7 9 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.