OpenZeppelin / OpenZeppelin/openzeppelin-upgrades
Use separate Solc inputs to verify different proxy contracts
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 658
- Forks
- 286
- PR merge metrics
- No merged PRs in 30d
Description
Currently the Solc input for all proxy-related contracts are packaged into one build-info.json file. When using this to verify source code on Etherscan, this causes the contracts for every different proxy kind to be included.
For example, even if the user is only using ERC1967Proxy, the source code for TransparentUpgradeableProxy would also be included in the verified source code.
To improve this, we should verify each proxy-related contract using its own Solc input for that contract and its dependencies only.
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 where proxy-related contracts are packaged into build-info.json and how those inputs are passed to Etherscan verification. Confirm the dependencies required by each proxy kind, then verify that each contract produces a separate Solc input containing only that contract and its dependencies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- solidity, typescript
- Domain
- blockchain, build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100