Revault Network
- Completed
-
Audit Report
Commissioned
16 Aug 2021
Completed
27 Sep 2021
Contracts Audited
ReVault ReVault.sol ReVault RevaUserProxy.sol RevaUserProxyFactory RevaUserProxyFactory.sol RevaChef RevaChef.sol RevaStakingPool RevaStakingPool.sol RevaLpStakingPool RevaLpStakingPool.sol RevaFeeReceiver RevaFeeReceiver.sol Zap Zap.sol ZapAndDeposit ZapAndDeposit.sol RevaToken RevaToken.sol vRevaToken vRevaToken.sol Timelock Timelock.sol View Audit Report
IssuesRisk SummaryFound Resolved Partially Resolved Acknowledged
(no change made)High 11 11 – – Medium 9 8 1 – Low 14 11 1 2 Informational 26 13 2 11 Total 60 43 4 13 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.