OpenZeppelin / OpenZeppelin/openzeppelin-upgrades
Ability to deploy proxy using create2
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 658
- Forks
- 286
- PR merge metrics
- No merged PRs in 30d
Description
It would be helpful if it were possible to define a salt when calling deployProxy which would indicate to use CREATE2 and deploy out a proxy at a deterministic address.
Happy to elaborate more, but for instance if I wanted to deploy the same upgradable proxy on two different chains, and make it so they have the same address, it wouldn't be possible when using this library.
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 tracing the deployProxy entry point in the upgrades plugin and identify how proxy deployment currently selects an address. Determine how a caller-provided salt would select CREATE2 while preserving upgradeable-proxy behavior. Done means the same proxy can be deployed at a deterministic address on multiple chains, with tests covering the new option.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100