OpenZeppelin / OpenZeppelin/openzeppelin-upgrades
Deploy BeaconProxy using create2: Proxy Implementation Verification error
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 658
- Forks
- 286
- PR merge metrics
- No merged PRs in 30d
Description
Hi, I used create2 to deploy a BeaconProxy but i not able verify implementation for BeaconProxy
it is error:
The proxy contract verification completed with the message:
A corresponding implementation contract was unfortunately not detected for the proxy address 0x1af9dee53d62a7124c81ad68d5ab76092f2b3f6a
Address Implementation: https://testnet.bscscan.com/address/0xa088a202e42223392D7eB441904cb5F5a00E1791#code
Address Beacon: https://testnet.bscscan.com/address/0x8Cc81d1f67a602f131C5F7b1f3D188d4fDd30fCC#code
Address Factory: https://testnet.bscscan.com/address/0x060D9f079a4Ee734F0E1d6A723EBB00Aa237f0b4#code
Address BeaconProxy: https://testnet.bscscan.com/address/0x1af9dee53d62a7124c81ad68d5ab76092f2b3f6a#code
Please help me!!!, thanks very much
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 linked Implementation, Beacon, Factory, and BeaconProxy deployments, along with the reported create2 deployment and verification error. Reproduce the verification attempt using the supplied addresses; done means identifying the cause of the missing implementation detection and documenting or implementing a verified resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- solidity
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100