Etherscan V2 #1388
Merged
Etherscan V2 #1388
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.
This PR updates our Etherscan integration to support the new Etherscan V2 API, as the V1 API is scheduled to be deprecated by the end of the month.
Following the official migration guide (Etherscan V2 Quickstart), the update introduces support for V2 by adding the required chainId parameter.
To ensure maximum compatibility and flexibility, support for V1 has been retained, allowing users to choose between V1 and V2 providers depending on their needs. This is particularly important in case certain chains or explorers (e.g., Snowtrace) diverge from Etherscan's V2 implementation or are not yet fully supported.
By default, V2 is now enabled for Ethereum, Avalanche, Base, BSC, and Arbitrum, which means any integrations using default configurations for these clients may be affected.
Additionally, the environment variable ETHERSCAN_API_KEY is now used as the unified API key across all supported chains.