[Aave-v3] Mumbai testnet addresses used by the dApp do not match the addresses on the dev doc
jkrivine opened this issue · comments
The addresses listed in the developper documentation for mumbai here
https://docs.aave.com/developers/deployed-contracts/v3-testnet-addresses
do not match the addresses that seem to be used by the dApp (also on mumbai). The dApp should either use the addresses of the doc, or the doc be updated to the dApp addresses:
"DAI": "0xc87385b5e62099f92d490750fcd6c901a524bbca",
"USDC": "0xF61Cffd6071a8DB7cD5E8DF1D3A5450D9903cF1c",
"WETH": "0x63e537a69b3f5b03f4f46c5765c82861bd874b6e",
...
"aWETH": "0xCa003B920F1CEcb4fe0Fe91B657E58a8E1EED04a",
"aDAI": "0x3D8477D93A0B036Ec3D180fA013848B628c5cb76",
"aUSDC": "0xc78fd49C2bAd9C8f41ddcE069e34F6a6A627d37f",
...
"addressProvider": "0x5343b5bA672Ae99d627A1C87866b8E53F47Db2E6"
'poolproxy': "0xEce3383269ccE0B2ae66277101996b58c482817B"
also verifiying the deployed contracts would tremendously help debugging!
better posted on the UI repo