Lesson 10: Contract Addresses Constant

[ghost]

I don’t fully understand the structure or usage of the contract addresses constant.

Why do we need an array of addresses for each chain?

Is it in case we create more contracts? Then how do we know the index of a particular contract we want to use?

Or does the front end assume we only have one contract, and the array is to store the addresses of previous versions of the contract we've deployed on a given chain? Then why does the LotteryEntrance component use the first element in the array when the 02-update-front-end deployment script pushes the new address into the array (making it the last element) - wouldn’t we want to use the most recent version of the contract?

[krakxn]

"Why do we need an array of addresses for each chain?" As you mentioned, it is to index each address in case we deploy multiple contracts on the same network.

"wouldn’t we want to use the most recent version of the contract?" I agree with this one - not sure why we are not using the recent one? As it defeats the purpose of indexing every address - the only plausible reason is that we are supposed to hardcode it and change it explicitly. Cheers

[ghost]

Hey @krakxn!

it is to index each address in case we deploy multiple contracts on the same network.

Sorry pal, do you mean the same contract multiple times (i.e. different versions of the same contract, e.g. ContractA * 5) or different contracts (e.g. ContractA and ContractB) or both?

[ghost]

The structure in lesson 15 (chain_id -> contract_name -> address[]) makes the intent clear. Though here Patrick does say "get the most recently deployed NftMarketplace", so using the address at the zeroth index must be a small mistake in the course (unless I'm missing something.)

[krakxn]

Yeah, seems like it. push inserts the element to the last index + 1