Best way to generate deploy artifact #4
Labels
question
Further information is requested
Comments
|
It should be The bytecode in the file is not used to check difference, hardhat-depliy actually fetch the transaction from the transactionHash field and check if the new source code + constructor argument matches |
|
As for generating deployment artifact from project like etherscan, this could be handled by an external tool, or even an hardhat plugin. You would still need to provide the address |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Which is the best way to generate deploy artifacts of a deployed proxied smart contract at a given public network?
I was able to do this once with the following set of manually written artifacts placed in
deployments/<network name>folder:This time I'm not being able to correctly define
<contract name>_implementation.jsonbyte code and because of this, hardhat is redeploying the implementation contract...Ideally, there should be an automated and straight forward way to get the deployment artifacts from from contracts already deployed in public networks. Any suggestions?
The text was updated successfully, but these errors were encountered: