Verify #161
Open
Verify #161
Conversation
This file contains 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.
Verify a recently deployed contract based on current values in the contract. If values that are set by constructor are updated after initial deployment this will fail.
usage example:
npx hardhat verifyOne [address] [contractName] [contractFilePath]this task is refactored from code i used to verify all current contracts, i don't this should be approved until we confirm its work for new contract deployments.
Note: sometimes verification fails due to optimization creating different bytecode. Use
compileOneto recompile the specific contract and try again.usage example
npx hardhat compileOne [contractName]