Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use hardhat-deploy for EVM contract deployment #811

Open
CyrusVorwald opened this issue Nov 17, 2022 · 0 comments
Open

Use hardhat-deploy for EVM contract deployment #811

CyrusVorwald opened this issue Nov 17, 2022 · 0 comments
Assignees
Labels
module: message center Relates to the message center module module: service handler Relates to the service handler module scope: task Granular task that does not necessarily impact an end user

Comments

@CyrusVorwald
Copy link
Contributor

CyrusVorwald commented Nov 17, 2022

What needs to be done

Write deploy scripts so that EVM contracts can be deployed to any EVM chain. Should be configured with named accounts where relevant. For example, the deployment contract owner is one distinct address and the fee owner is another distinct address.

Why it needs to be done

Makes EVM deployment faster and its configuration more human readable. This also makes deployment dependencies a lot more straightforward.

Acceptance Criteria

I can easily deploy locally and to testnet for both SNOW and BSC without changing anything other than network configuration parameters.

@CyrusVorwald CyrusVorwald added module: service handler Relates to the service handler module module: message center Relates to the message center module scope: task Granular task that does not necessarily impact an end user labels Nov 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
module: message center Relates to the message center module module: service handler Relates to the service handler module scope: task Granular task that does not necessarily impact an end user
Projects
None yet
Development

No branches or pull requests

2 participants