@aave-dao/aave-v3-origin v3.3.0
Aave V3.3 Origin

Aave v3.3 complete codebase, Foundry-based.
Dependencies
- Foundry, how-to install (we recommend also update to the last version with
foundryup) - Lcov
- Optional, only needed for coverage testing
- For Ubuntu, you can install via
apt install lcov - For Mac, you can install via
brew install lcov
Setup
cp .env.example .env
forge install
# required for tests & linting
npm installTests
- To run the full test suite:
make test - To re-generate the coverage report:
make coverage - To run the enigma fuzzing suite, checkout the dedicated docs HERE
Documentation
- Aave v3 technical Paper
- v3 to v3.0.2 production upgrade
- Aave v3.1 features
- Aave v3.2 features
- Aave v3.3 features
- v3.1 to v3.2 production upgrade
- v3.2 to v3.3 production upgrade
- Set Ltv to 0 on Freeze Feature State diagram
Security
Aave v3.1 is an upgraded version of Aave v3, more precisely on top of the initial Aave v3 release and a follow-up 3.0.2 later update.
The following are the security procedures historically applied to Aave v3.X versions.
-> Aave v3
-> Aave v3.0.1 - December 2022
-> Aave v3.0.2 - April 2023
-> Aave v3.1 - April 2024
- Certora
- MixBytes
- An internal review by SterMi on the virtual accounting feature was conducted on an initial phase of the codebase.
- Cantina competition report
- Additionally, Certora properties have been improved over time since the Aave v3 release. More details HERE.
-> Aave v3.2 - September 2024
Stable Rate and Liquid eModes
Liquid eModes
-> Aave v3.3 - January 2025
Deficit tracking & Liquidation optimizations
In addition, Enigma Dark has adapted the Foundry-based fuzzing invariant suite to the Aave v3.3 codebase.
Bug bounty
This repository will be subjected to this bug bounty once the Aave Governance upgrades the smart contracts in the applicable production instances.
License
Copyright © 2024, Aave DAO, represented by its governance smart contracts.
The BUSL1.1 license of this repository allows for any usage of the software, if respecting the Additional Use Grant limitations, forbidding any use case damaging anyhow the Aave DAO's interests. Interfaces and other components required for integrations are explicitly MIT licensed.
11 months ago