Hi,
I’m trying to verify the proxy contract on Mumbai Testnet Network but I’m facing problems. Help me to verify the proxy contract.
Here is the address for verification :
Proxy: 0x6aa8c5cbb1a2a4fa3b27d1711f411bc0ab27193a
What block explorer are you trying to verify on?
I’m trying to verfiy on matic testnet name mumbai tesetnetwork : https://explorer-mumbai.maticvigil.com/
Sorry I have added wrong address here is right one : 0xbFC244027E0D16F483E8A552B00f46278A5439D9
Skyge
May 22, 2021, 8:30am
6
Which package version do you use?
Compiler version : version: “0.8.3”@openzeppelin /contracts-upgradeable : ^4.0.0
Unfortunately can’t verify until solc standard JSON input is support for verification.
This seems to be tracked in the following issue:
opened 08:41PM - 22 Jul 20 UTC
contract verification
waiting on feedback
*Describe your issue here.*
The "Verify&Publish" for blockscout suggests to u… se source flattener, and upload the entire source as a single file.
However, with the latest solc version (0.6.x), this is sometimes NOT possible:
The "opengsn" project uses the ABIEncoderV2, but some external sources don't use it.
As a result, when flattening the file the "pragma ABIEncoderV2" is applied to entire code, instead of just parts.
The consequence is that the generated bytecode for flattened file is different.
We already deployed the contract to **mainnet**, **kovan**, **ropsten** along with source code - but currently we found out that we **can't upload source code** for the XDAI deployment.
For deployment to ethereum network, we uploaded the "standard-json" file that was used to compile, and thus kept the separate files separate.
https://kovan.etherscan.io/address/0xA17C8F25668a5748E9B80ED8Ff842f8909258bF6#code
The same contract was deployed to xDAI, but currently we can't upload its sources: https://blockscout.com/poa/xdai/address/0xA58B6fC9264ce507d0B0B477ceE31674341CB27e/contracts
### Steps to reproduce
```
git clone https://github.com/opengsn/gsn.git && cd gsn && yarn && truffle compile
```
the code is generated in build/contracts/RelayHub.sol
Then if you flatten the contracts/RelayHub.sol (and remove duplicate SPDX comments and "pragma ABIEncoderV2" , since flatteners don't recognize them yet) and compile it, you get slightly different output, enough to be rejected by "Verify&Publish" ...
### Expected behaviour
Verify&Publish should accept a single "json-standard" file instead of input file.
Simply, if the input starts with ` {"language":"Solidity","sources":... `
try to parse it as a **json-standard** input.
So give me a suggestion, what I can do ??
As far as I can tell best you can do right now is to show support for the feature request in the GitHub issue I mentioned.
Another option is to do a manual proxy deployment with a single-file proxy contract that you will then be able to verify. We won’t be able to help with this though.