Aave V2 (aave-v2)

​

When to use it

• The previous Aave generation, where a chain still runs its market. Where a chain has both, Aave V3 is the current market (aave-v3).

​

Pitfalls for a program

• The supply call is deposit, not supply; approve the LendingPool first.
• onBehalfOf receives the aTokens. The caller is the Pot, so pot keeps them in the Pot, not in the user’s wallet: choose which, and pass the wallet as a main parameter to deliver them.
• aTokens are rebasing: measure balances as deltas.
• A frozen reserve refuses new deposits: check the reserve accepts them before relying on it.
• Borrowing and liquidation work as in Aave V3, by health factor.

​

In a Sauce program

function main(onBehalfOf: Address, amount: Uint256) {
  USDC.approve(AaveV2.LendingPool, amount);
  AaveV2.LendingPool.deposit(USDC, amount, onBehalfOf, 0);
}

​

Notes

• interestRateMode: 1 = stable, 2 = variable. Most users use variable rate
• referralCode is always 0 (referral program inactive)
• Legacy protocol — consider Aave V3 for new deployments
• All deposit/repay operations require prior ERC-20 approval to the LendingPool address

​

Its names in a program

function main() {
  // Ethereum's lendingPool, `0x7d2768dE32b0b80b7a3454c06BdAc94A69DDc7A9`.
  require(AaveV2.LendingPool != 0);
}

​

Deployments

​

ABI

​

LendingPoolABI

• deposit(address asset, uint256 amount, address onBehalfOf, uint16 referralCode)
• withdraw(address asset, uint256 amount, address to) returns (uint256)
• borrow(address asset, uint256 amount, uint256 interestRateMode, uint16 referralCode, address onBehalfOf)
• repay(address asset, uint256 amount, uint256 rateMode, address onBehalfOf) returns (uint256)

​

Next steps

• Protocols: the other protocols, by what they do.
• Protocols and tokens: calling a contract by its namespace, or through its ABI.
• Glossary: the words these pages use, in plain terms.