Lesson 13: Is using lendingPoolAddressesProvider necessary?

[SimasG]

We're using Aave's lendingPoolAddressesProvider contract to fetch our lending pool's address in our getLendingPool function. However, it seems that we're fetching just the same address we could've found hardcoded in Aave's docs.

  const lendingPoolAddressesProvider = await ethers.getContractAt(
    "ILendingPoolAddressesProvider",
    "0xB53C1a33016B2DC2fF3653530bfF1848a515c8c5"
  );

  const lendingPoolAddress =
    await lendingPoolAddressesProvider.getLendingPool();

  // ** Both are identical
  console.log(`Lending pool address: ${lendingPoolAddress}`);
  console.log(
    `Lending pool address on Aave (raw): 0x7d2768dE32b0b80b7a3454c06BdAc94A69DDc7A9`
  );

Am I missing something or is it unnecessary to use lendingPoolAddressesProvider ?

[RoboCrypter]

@SimasG : Yes, It is necessary because from lendingPoolAddressesProvider we our lendingPoolAddress!

Which we need in depositing, borrowing and also repaying. and we are doing it programmatically!

[RoboCrypter]

@SimasG : @alymurtazamemon Clarified more in the below comment! Why we are not hard coding it!

[alymurtazamemon]

@SimasG Yes, we can hardcode it but we are doing it programmatically, the same way we use etherscan for verification.

[alymurtazamemon]

@SimasG This way you do not have to worry about address changes.

[othaime-en]

^ especially if and when there is an upgrade to the contract that leads to a contract-address change. This versatility is absolutely essential for guaranteed efficiency and validity of our program.

[SimasG]

I see, that explains it. Thank you all so much!