OpenZeppelin / OpenZeppelin/openzeppelin-upgrades
Ensuring deployProxy does not deploy the implementation
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 658
- Forks
- 286
- PR merge metrics
- No merged PRs in 30d
Description
Given the high costs of deploying to Ethereum mainnet, understandably users want to be sure that rerunning deployProxy will not redeploy an implementation contract that they already deployed in a previous run that timed out. We could have a flag that asks deployProxy to fail if it has to deploy the implementation before proceeding to deploy the proxy.
See a post in the forum about this.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the deployProxy entry point and review how it handles implementation deployment and reruns. Read the linked forum discussion for the partial-deployment context. Done means deployProxy can be instructed to fail before proceeding when it would need to deploy the implementation again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100