Contract verification on Optimism, Arbitrum and Mainnet

[istankovic]

Create a script to verify contracts on

• [ ] Optimism
• [ ] Mainnet
• [ ] Arbitrum

It can be called by python scripts/verify-contracts.py <artifacts_dir> <rpc_file>

Acceptance criteria

• [ ] Implement the script using ape-etherscan
• [ ] Deploy goerli and test it

[taleldayekh]

Waiting for https://github.com/eth-brownie/brownie/issues/1591

[fredo]

This should be pulled into the backlog once we are working on the new deployment infrastructure. We need to find a solution though. An alternative approach which turned out to be successful is verification on the explorer directly. According to @compojoom description we need to fold all imports into one file. For the current version such a document can be found here. In any case, this should also be automated upon deployment.

[andfletcher]

I added this issue to the Rework deployment infrastructure Epic

[istankovic]

Now that we have ape, we need to consider using it for contract verification instead of rolling our own solution. At least we should have an idea about the following:

• how hard it is to add support for contract verification on new chains in ape
• the extent of new dependencies we would be using inside the beamer Python package (excluding tests)
• possible minimization of dependencies
• potential changes in import times of beamer

[bilbeyt]

Whenever we need to add a chain we need to create pr for ape-etherscan that will update client.py, config.py and utils.py for the new chain. If the chain plugin is not released by apeworx, we need to create the repo with plugin and transfer the ownership to them. It basically needs to use https://github.com/ApeWorX/project-template as template and like in here https://github.com/ApeWorX/ape-optimism/tree/main/ape_optimism implements ecosystem.py. and init.py

[andfletcher]

needs to be checked again since the artifact structure changed.

[andfletcher]

No tests for this issue.