chore: use Etherscan API V2 for contract verification#117
Draft
anxolin wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds an
[etherscan]section tofoundry.tomlsoforge verify-contract/forge script --verifyuse the Etherscan API V2 endpoint for all supported chains (mainnet, gnosis, sepolia, arbitrum, bnb, linea).Why
The legacy per-explorer V1 APIs (e.g.
api.gnosisscan.io) have been shut down. Verifying against them now fails with:V2 uses a single host (
api.etherscan.io/v2/api) with the chain id passed as a query parameter, and a singleetherscan.ioAPI key works across every chain. This config points each chain at the V2 endpoint so verification works out of the box.Test plan
https://api.etherscan.io/v2/api?chainid=100and succeed instead of returning the V1 deprecation error.