Smart Contract Risks
Smart contracts can contain software bugs or other vulnerabilities within the protocol code and the underlying reserve tokens. To mitigate these risks, HypurrFi is based on Aave V3’s open-source code, which has undergone significant third-party professional audit. Specifically it uses the Aave V3.0.2 codebase. Notable code differences between HypurrFi and Aave V3 include:- Stable debt is not supported.
- The RewardsController is not available currently.
- Reserve assets are configured specifically for the Hyperliquid EVM ecosystem.
Smart Contract Audits
HypurrFi Audits
V3.0.2 Audits
V3.0.1 Audits
- Contract Review - Dec 23 2022
- Formal Verification of Aave V3 upgrade to V3.0.1 - Nov 17 2022 - Dec 15 2022
- Smart Contract Audit Report - Dec 22 2022
V3 Audits
- Smart Contract Audit Report - Jan 27 2022
- Smart Contract Security Assessment Report - Jan 27 2022
- Formal Verification of Aave Protocol V3 - Nov 12 2021 - Jan 24 2022
- Smart Contract Audit Report - Jan 14 2022
- Security Assessment Report - Jan 7 2022
- Smart Contract Audit Report - Jan 11 2021
Fraxlend Audits
- Fraxlend & Fraxferry Security Review - November 2022
- Fraxlend & veFPIS Security Review - January 2023