Verify hardhat upgrades Beacon and BeaconProxy on mumbai testnet

[shashank]

I've used the hardhat upgrades plugins to deploy Beacon and BeaconProxy on polygon mumbai testnet, but perhaps there aren't any matches on the testnet. Can you help with verification of these?

Beacon contract - 0xA54E7a5D3dEEB0b83aeBb94040EE267EFe9B6089
BeaconProxy contract - 0xD86fa19bda2FAE5D8199DAff4A9C6F2fA3C52e6A

The guides here don't really speak for beacon verification I think

How to verify a contract on Etherscan/BscScan/PolygonScan

Make sure to read this post before asking a question about verification. If your issue is not addressed here, just leave a comment below. If you want to pay someone to do the verification for you, create a post in Developer Wanted. This guide applies to all Etherscan instances, including all of the following as well as their testnet explorers: etherscan.io (Ethereum) bscscan.com (Binance Smart Chain) polygonscan.com (Polygon) snowtrace.io (Avalanche) Recommendations Practice in testnet Be…

Verifying BeaconProxy on etherscan

I have been struggling to get proxies deployed via a factory contract implementing the UpgradeableBeacon pattern to verify on etherscan. The contract verifies when I deploy it directly, but not the proxies. Is there something unique to the beacon pattern that makes verifying proxies more complicated?

[frangio]

Pinging @ericglau so he can verify these.

[ericglau]

Hi @shashank, the beacon proxy and beacon contracts have now been verified on Polygon Mumbai.

We've also added info about beacon proxies to this section of the guide: How to verify a contract on Etherscan/BscScan/PolygonScan , and the Solc JSON Input provided there can be used to verify beacon proxies and beacons on other networks as well.

[shashank]

Thank you @ericglau and @frangio for referring!