This repository contains an up-to-date registry of all addresses of the Aave ecosystem's smart contracts, for its usage in Solidity codebases.
The goal is for Solidity developers to have the most integrated environment possible when they want to develop on top of Aave, by just importing a package with all the necessary addresses to interact with.
With Foundry installed and being in a Git repository:
forge install bgd-labs/aave-address-bookImport a pool specific collection of addresses & interfaces:
import {AaveV2Ethereum} from "aave-address-book/AaveV2Ethereum.sol";
import {AaveV3Avalanche} from "aave-address-book/AaveV3Avalanche.sol";Included addresses:
// v2 libraries
ILendingPoolAddressesProvider POOL_ADDRESSES_PROVIDER;
ILendingPool POOL;
ILendingPoolConfigurator POOL_CONFIGURATOR;
IAaveOracle ORACLE;
IAaveProtocolDataProvider AAVE_PROTOCOL_DATA_PROVIDER;
address POOL_ADMIN;
address EMERGENCY_ADMIN;
ICollector COLLECTOR;
// v3 libraries
IPoolAddressesProvider POOL_ADDRESSES_PROVIDER;
IPool POOL;
IPoolConfigurator POOL_CONFIGURATOR;
IAaveOracle ORACLE;
IAaveProtocolDataProvider AAVE_PROTOCOL_DATA_PROVIDER;
IACLManager ACL_MANAGER;
address ACL_ADMIN;
ICollector COLLECTOR;
address DEFAULT_INCENTIVES_CONTROLLER;
address DEFAULT_A_TOKEN_IMPL_REV_1;
address DEFAULT_VARIABLE_DEBT_TOKEN_IMPL_REV_1;
address DEFAULT_STABLE_DEBT_TOKEN_IMPL_REV_1;Import addresses and interfaces to interact with Governance:
import {AaveGovernanceV2} from "aave-address-book/AaveGovernanceV2.sol";Included addresses:
IAaveGovernanceV2 GOV;
address SHORT_EXECUTOR;
address LONG_EXECUTOR;
address ARC_TIMELOCK;Import miscellaneous addresses and interfaces relevant to the aave protocol:
import {AaveMisc} from "aave-address-book/AaveMisc.sol";Included addresses:
IAaveEcosystemReserveController AAVE_ECOSYSTEM_RESERVE_CONTROLLER;
address ECOSYSTEM_RESERVE;While there is a index import available in "aave-address-book/AaveAddressBook.sol", we only recommend using it in tests.
Foundry currently does not eliminate unused code for verification.
This results in rather gigantic verifications when using the index file import from aave-address-book/AaveAddressBook.sol.
For production code we therefore recommend to use pool specific libraries (Aave[Version][Network][?SubPool]) exported from aave-address-book like AaveV2Ethereum for the V2 Ethereum pool.
npm i @bgd-labs/aave-address-bookimport * as pools from "@bgd-labs/aave-address-book"; // wildcard import
import { AaveV2Avalanche } from "@bgd-labs/aave-address-book"; // import specific pool
// all variables available on solidity version are available in javascript as well
console.log(AaveV2Avalanche.POOL_ADDRESSES_PROVIDER);
// "0xa97684ead0e402dC232d5A977953DF7ECBaB3CDb"
// in addition the chainId of the respecitve addresses is exported alongside
console.log(AaveV2Avalanche.CHAIN_ID);
// 43114The library is generated based on the config file located in scripts/config.ts. You can regenerate the files by running yarn start.
forge updateforge buildforge testTo list a new pool in the address book, you simply need to add a new pool in the pools config and run yarn start.
a) Adding an address that can be optained via onchain calls so it doesn't need to be hardcoded on the configs:
To achieve an addition here you need to add the address to the respective v2 type and/or v3 type and adjust the generator scripts accordingly. New types should be added to the AaveV2 and AaveV3 files.
b) Adding an address that cannot be optained via onchain calls so it needs to be manually maintained:
To achieve an addition here, you need to alter the additionalAddresses section on the pool type and add your address to the respecive pools. Additional addresses will currently be exported as type address. There's currently no possibility to define a custom type.
In any case you need to run yarn start afterwards and commit the altered artifacts.