Use Etherscan API for contract code verification #52
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.
Description
This PR introduces the
yarn run verify
command for verifying deployed contracts.Motivation
This allows for automated contract verification without having to interact with the Etherscan frontend for verifying contracts.
Design
The
yarn run verify
command requires the name of the contract to be passed in as a parameter. This makes it hard to additionally pass in the network parameter too. Previous we had two deploy commands, one for Kovan and one for Mainnet. In replacement of that we introduce theNETWORK
environmental variable, that should be passed in with the command.For example:
or
Unresolved Issues
Ideally, the contract verification should not be a separate step but should be a part of the deployment stage. After each contract deploy, that contract should automatically be verified, rather than having to specify which contracts to verify. This can be done by extending the
truffle-deployer
and adding a post deploy hook of some kind, in combination withsol-merger
ortruffle-flattener
and the Etherscan API interface in this PR.