OpenZeppelin / OpenZeppelin/openzeppelin-upgrades
Provide a way to estimate gas for proxy deployments
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 658
- Forks
- 286
- PR merge metrics
- No merged PRs in 30d
Description
Deployments using the upgrades plugins can involve deploying a number of contracts, some of which can include the implementation, proxy admin, proxy contract, beacon contract.
If an account does not have sufficient funds to cover deploying all of those contracts, only some of those contracts may be deployed. This results in either needing to add additional funds to the account, or users might just start using the implementation contract directly.
As suggested in this forum post, consider providing a way to estimate gas for all of the contracts that will be deployed by a command.
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 by reviewing the upgrades plugins' deployment command and the linked forum discussion. Identify how implementation, proxy admin, proxy, and beacon contracts are selected for deployment, then define an estimate that covers the complete deployment set. Done means users can obtain the aggregate gas estimate before deploying.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100