OpenZeppelin / OpenZeppelin/openzeppelin-upgrades
add option to return populated upgrade transaction
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 658
- Forks
- 286
- PR merge metrics
- No merged PRs in 30d
Description
Returning a populated upgrade transaction would allow me to craft and send the transaction through a multisig instead of the buidler signer
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
No file or test is named in the issue. Start by locating the upgrade transaction construction and existing deployment or upgrade entry points, then trace how the builder signer submits them. Done means an upgrade transaction can be returned populated for multisig submission without requiring the builder signer, with coverage for that flow.
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
- 42/100