Fix verification process #397
Open
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 the hardhat-verify package to v2.1.3, which uses Etherscan's API v2.
Etherscan's API v2 uses a single API URL for all supported networks, which includes Arbitrum One, Nova and Sepolia. Now within the request sent to the API, the chain id of the network is included. Only Etherescan's API keys are valid now (the ones obtained from network-specific explorers, like Arbiscan, are no valid anymore).
Also, hardhat-verify@v2.1.3 includes arbitrumSepolia in their predefined networks, so there's no need to add it as a custom network anymore.
Finally, verification in sourcify has been included in the configuration, and the internal documentation has been updated with the same format.