Add Etherscan configuration for new networks#240
Conversation
🫡 |
|
@kuzdogan Etherscan verification is always, constantly painful to obtain for one reason or another but Sourcify in the last (at least) year has been a breeze to use, never had any issue when I needed to verify a contract, and all this useful contract data is easily and transparently available. Great job and thanks for the service! |
| arbitrumOne: ETHERSCAN_API_KEY, | ||
| base: ETHERSCAN_API_KEY, | ||
| optimisticEthereum: ETHERSCAN_API_KEY, | ||
| polygon: ETHERSCAN_API_KEY, |
There was a problem hiding this comment.
Did this work for you using the same key as other chains??
I tried deploying today with Etherscan API Key (on another project) and it didn't work.
I created a new key specifically for polygonscan.com and then it did.
There was a problem hiding this comment.
yes, you need to create an API key per block explorer.
There was a problem hiding this comment.
This is luckily going to change soon, see foundry-rs/foundry#9196.
| sepolia: ETHERSCAN_API_KEY, | ||
| arbitrumOne: ETHERSCAN_API_KEY, | ||
| base: ETHERSCAN_API_KEY, | ||
| optimisticEthereum: ETHERSCAN_API_KEY, |
There was a problem hiding this comment.
I thought for now avalanche and polygon
There was a problem hiding this comment.
#239 also deployed the other two, so I verified those as well.
mateo-mro
force-pushed
the
support-multiple-networks
branch
from
bc6649b to
c6bac3f
Compare
4 participants
Description
Add the necessary configuration lines for allowing contract verification on the Block explorers of the networks introduced in #239.
BNB was already verified. Optimism and Polygon just worked out of the box. Avalanche defaults to Snowtrace, so I had to include a custom configuration for that network in order to use SnowScan and used:
I also enabled Sourcify because why not?
Test Plan
Check out the contract addresses on the block explorer.