How to verify upgradeable contract on opbnb-testnet?

[liweimilan]

Hi:
I deployed a upgradeable contract on opbnb-testnet. and my implementation contract was verified at https://testnet.opbnbscan.com/address/0x302DE2793B49195605D46eb718E34D9bcd6A4385#code

ProxyAdmin address : 0x68B8a3Cf23CbDbdCDd849955be6da198ac8C7A0A
Proxy address: 0x2Db3498F07E4B6567D25eD275A2fc557d358921b

please help me to verify them or tell me how to do?

Thanks.

[barakman]

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…

[liweimilan]

I have seen this post, and the proxy contract is not verified, and I want to know how to use the json file in the guide?

Does that mean I verify with the browser and select Compiler Type with Standard-Json-Input?

Thanks.

If proxy is not verified

Proxy contracts, beacons, and the ProxyAdmin should be verified automatically as "Similar Match", because we have verified other instances of the same code. On some networks, there may not be a verified instance and the contract you deploy may show up as unverified. In that case, you can verify this contract using the Solc JSON Input shared below, or feel free to contact us in Upgrades to assist.

[ericglau]

Your proxy contracts are verified now. Yes, normally you can verify through browser with Standard-Json-Input (I've just updated the json files attached to that post since they were out of date before).