Lesson 13 - Error when using @aave/core-v3 to get pool address

[levblanc]

Hi,

I am trying to use @aave/core-v3 with lesson 13 and met error on getting the pool address. Please help.

Error details

Error: call revert exception [ See: https://links.ethers.org/v5-errors-CALL_EXCEPTION ] (method="getPool()", data="0x", errorArgs=null, errorName=null, errorSignature=null, reason=null, code=CALL_EXCEPTION, version=abi/5.7.0)
    at Logger.makeError (/Users/levblanc/projects/web3-defi-hardhat/node_modules/@ethersproject/logger/src.ts/index.ts:269:28)
    at Logger.throwError (/Users/levblanc/projects/web3-defi-hardhat/node_modules/@ethersproject/logger/src.ts/index.ts:281:20)
    at Interface.decodeFunctionResult (/Users/levblanc/projects/web3-defi-hardhat/node_modules/@ethersproject/abi/src.ts/interface.ts:427:23)
    at Contract.<anonymous> (/Users/levblanc/projects/web3-defi-hardhat/node_modules/@ethersproject/contracts/src.ts/index.ts:400:44)
    at step (/Users/levblanc/projects/web3-defi-hardhat/node_modules/@ethersproject/contracts/lib/index.js:48:23)
    at Object.next (/Users/levblanc/projects/web3-defi-hardhat/node_modules/@ethersproject/contracts/lib/index.js:29:53)
    at fulfilled (/Users/levblanc/projects/web3-defi-hardhat/node_modules/@ethersproject/contracts/lib/index.js:20:58)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  reason: null,
  code: 'CALL_EXCEPTION',
  method: 'getPool()',
  data: '0x',
  errorArgs: null,
  errorName: null,
  errorSignature: null,
  address: '0xa97684ead0e402dC232d5A977953DF7ECBaB3CDb',
  args: [],
  transaction: {
    data: '0x026b1d5f',
    to: '0xa97684ead0e402dC232d5A977953DF7ECBaB3CDb',
    from: '0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266',
    gasLimit: BigNumber { _hex: '0x01bad458', _isBigNumber: true }
  }
}

I really have no ideas why it says call exception, because I confirm that:

• the lendingPoolAddressProvider is successfully getting back the deployed contract
• getPool function (should be v3 equivalent of getLendingPool) exists
• getPool function requires no params, doc here

  const lendingPoolAddressProvider = await ethers.getContractAt(
    'IPoolAddressesProvider',
    poolAddressProvider,
    account
  );

  console.log(
    '>>>>>> lendingPoolAddressProvider.getPool',
    lendingPoolAddressProvider.getPool  // function exists
  );

  const lendingPoolAddress = await lendingPoolAddressProvider.getPool();
  console.log('>>>>>> lendingPoolAddress', lendingPoolAddress);  // => throws above exception

My repo

Here is my repo: https://github.com/levblanc/web3-defi-hardhat
I've included debug logs in scripts/aaveBorrow.js.

Please run:

1. yarn hardhat node to spin up a local node
2. yarn hardhat run scripts/aaveBorrow.js to trigger the script and error will be logged.

Please PR to the fix branch if you found anything. Thanks in advance.

[alymurtazamemon]

@levblanc Like we were using "@aave/protocol-v2": "^1.0.1", I am not sure if they have converted to the core package or is there any v3 version available for "@aave/protocol-v2.

Are you using it intentionally core-v3?

[levblanc]

Hi @alymurtazamemon ,

Yes, I use v3 intentionally. Because it's now marked as main version on official site, and I want my code to be updated as well.

Code for v3 version is here https://github.com/aave/aave-v3-core, I installed it as a dev dependency in my repo.

I've checked both v2 & v3 repos, the folder structures looks very similar, with contracts and interfaces file renaming, so I think v3 is an officially upgraded repo for v2.

[rstrategist]

Aave V3 works fine. You just need to:

1. get the code for IPool.sol and IPoolAddressesProvider.sol from:
   https://github.com/aave/aave-v3-core/tree/master/contracts/interfaces

2. update your brownie-config dependencies to e.g.:
   aave/aave-v3-core@1.19.2

3. And get the pool address provider address from the deployed contracts list:
   https://docs.aave.com/developers/deployed-contracts/v3-mainnet/ethereum-mainnet
   https://etherscan.io/address/0x2f39d218133AFaB8F2B819B1066c7E434Ad94E9e

4. Make small changes to aave_borrow.py to call the new interfaces and their functions, e.g. interface.IPool and .getPool()

My working code at: https://github.com/rstrategist/Solidity/tree/main/Learning/aave_brownie_py

[krakxn]

What was the initial shell command for the subsequent terminal in the description?

[krakxn]

@krakxn No, I didn't make any changes. Please clone and you will see the initial error.

Thanks :)

Did you complete the lesson? If so, the code is incomplete and I can make additions for the logic to be correct.

[levblanc]

No, the error is blocking me and the lending pool needed for following logic, I couldn't complete the lesson with V3.

I'm now continuing the lesson with V2 on another branch locally.

Feel free to make changes on the fix branch, it's in sync with the V3 code on master. Thanks :)

[krakxn]

@levblanc

Is V2 working properly?

I tried debugging and trying all sorts of fixes but that does not seem to affect the error one bit besides just slight additions in the logged metadata. :(

[levblanc]

Yes, I complete the lesson with V2 already.

Let's just ignore the error for now. Thank you very much for you help!

[krakxn]

Good luck!

[levblanc]

@alymurtazamemon @krakxn @othaime-en

I think I found something: the LendingPoolAddressesProvider deploy address.

On v2

When I click it's mainnet address link on this page:
https://docs.aave.com/developers/v/2.0/deployed-contracts/deployed-contracts

It goes to Etherscan:
https://etherscan.io/address/0xb53c1a33016b2dc2ff3653530bff1848a515c8c5#code

On v3

Deployed contracts are on many different chains, and in my config, I used the Polygon one:
https://docs.aave.com/developers/deployed-contracts/v3-mainnet/polygon

The address link for LendingPoolAddressesProvider points to Polygonscan:
https://polygonscan.com/address/0xa97684ead0e402dC232d5A977953DF7ECBaB3CDb#code

and seems this address does not have a record on Etherscan:
https://etherscan.io/address/0xa97684ead0e402dC232d5A977953DF7ECBaB3CDb

Possible Cause of Error

In my local, I am forking Ethereum mainnet following Patrick's guide, but the deployed contract address doesn't exist on my fork.

This brings me to a further queries

1. Aren't all mainnet chains in sync???

2. Even with my polygon address config, the following chunk of code returns the contract successfully.
   If this address does not exist on my local fork, why can my code get the contract info?

  const lendingPoolAddressProvider = await ethers.getContractAt(
    'IPoolAddressesProvider',
    poolAddressProvider,
    account
  );

  console.log(
    '>>>>>> lendingPoolAddressProvider',
    lendingPoolAddressProvider   // this can show the contract info with no issue
  );

[levblanc]

@alymurtazamemon
If the cause of my error is using a Polygon address for LendingPoolAddressesProvider, which does not exist on my local fork of the Ethereum mainnet, why the following code chunk can still run and logging out the contract info with no issue?

  const lendingPoolAddressProvider = await ethers.getContractAt(
    'IPoolAddressesProvider',
    poolAddressProvider,
    account
  );

  console.log(
    '>>>>>> lendingPoolAddressProvider',
    lendingPoolAddressProvider   // this can show the contract info with no issue
  );

If the contract does not exist on Ethereum mainnet, this should return error I think?

[alymurtazamemon]

@levblanc Actually I have created an issue about the new addresses of lesson 13 and will discuss it with Patrick then I can answer this

[alymurtazamemon]

@levblanc As you said yes new addresses are not on the Ethereum chain and I think it is coming from the POS eth chain but I have to discuss it first with Patrick then I can answer more clearly.

[levblanc]

@alymurtazamemon

No worries!

Btw, I have a further query on my Lesson 10's discussion, mainly about how MetaMask talk to the blockchain, would you please take a look as well?

Thank in advance.

[alymurtazamemon]

@levblanc It is answered.

[Samboy76]

I have the exact same issue with Polygon, Arbitrum, Avalanche chains when attempt to use their deployed PoolAddressProvider addresses for these chains. It works perfectly under Ethereum and as able to get hold of a flashloan as per the docs, but unfortunately, not for the other chains.

I´ve raised an issue on Aave v3 GitHub aave/aave-v3-core#805 but not getting any response or assistance on this matter.

Would appreciate any help or guidance to resolve.

Thank you

[levblanc]

Hi, in order to finish the course asap, I switched back to v2.
Getting the whole idea is more important than using the latest release.