Lesson 10: ContractNotFound: No contract deployed

[aloyboi]

I am trying to run get_weth .py & this is the error I am facing.
It is saying the mainnet weth token contract address is not deployed for "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2"

brownie-config.yaml

get_weth

I am using mainnet-fork-dev which was created a few lessons back

Another quick question: Why do I have to run Ganache client when I want to run on mainnet-fork-dev? Is it not forked from my Alchemy node? Closing Ganache client gives me "Unable to launch local RPC client." error.

[cromewar]

Hello @aloyboi
Be sure to have the alchemy configuration to development like this:

The weth token is this one:
'0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2'
remember to respect the upper and lower case letters.

The reason we use ganache is because we are not deploying to a network with persistency, we are just Mocking the mainnet.

[cromewar]

Seems the weth token addresses have changed check this out to the get the new ones: https://docs.aave.com/faq/testing-aave

[aloyboi]

does not seem like the weth token address changed, either that or I cannot find the new address.

The code runs smoothly on Kovan network but not on mainnet fork.

Does this have to do with funding of the mainnet-fork account? Where does it even get its funds?

[cromewar]

No I think is due to the address, as mainnetfork is using the weth token deployed on mainnet I know that token changes between versions of aave and on version v2 is different, cannot find either which one is it.

[aloyboi]

how do i tell which version of aave I should be using?

from what I am seeing seems like Ethereum mainnet is not available on V3 yet? So we should be using v2, & the weth token address looks the same

[cromewar]

I'll try to make more research on this, @PatrickAlphaC a hand on this one pal?