OpenZeppelin / OpenZeppelin/openzeppelin-upgrades
Document retry functionality in FAQ for partial deploy
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 658
- Forks
- 286
- PR merge metrics
- No merged PRs in 30d
Description
Community members are reporting partial deployments due to lack of funds. A combination of high gas prices for network congestion and the price of Ether.
We should document how OpenZeppelin Upgrades Plugins retries partial deployments picking up where it left off.
There have been the following queries:
https://forum.openzeppelin.com/t/partial-deploy-for-upgradeable-contract/5444
https://forum.openzeppelin.com/t/deployed-to-mainnet-but-errored-with-insufficient-funds/5006
https://forum.openzeppelin.com/t/deployment-tx-timed-out-deployed-implementation-but-not-proxy/5332
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 reading the three linked OpenZeppelin forum discussions and locate the repository's existing FAQ. Document how the Upgrades Plugins resume partial deployments after insufficient funds or a timeout, including the cases described in those discussions. Done means the FAQ answers these recurring questions clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100