-
Notifications
You must be signed in to change notification settings - Fork 227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot verify a contract with construct args and created within another contract #350
Comments
I'm sure the yarn hardhat verify --network zkSyncTestnet 0x22EA9D66eA20D0826444B9716Af4261Ce98b51Ba 100 Still not work. Your verification ID is: 34388
Error in plugin @matterlabs/hardhat-zksync-verify: Constructor arguments are not correct |
I tried looking for a solution from discord, and found a similar question |
Hi @zkbenny, this is a known bug where the verification of the smart contract deployed from another contract expects parent's constructor args. |
@FilipTxFusion Thanks, could you please fix this issue as soon as possible, if the contract cannot be open source and we cannot gain the trust of users |
@FilipTxFusion bumping this issue as we are also trying to verify a BeaconProxy, deployed from within a different contract. Getting an out-of-bound error, because I think it tries to decode tx params as constructor arguments, but they are different. |
I understand, thanks for reporting it. |
Hi.. Is this issue resolved ? still getting the: |
Hi @FilipTxFusion Does this problem solved? I see the official contract of zkSync L2StandardERC20 has been verified. |
I create a verify example project follow the guide Verify Contracts with Hardhat. Deploy and verify of the Greeter contract are ok, but verify a contract with construct args and created within another contract failed with message:
Here are two contracts:
DeployFactory
andProxy
, when deploy aDeployFactory
, aProxy
with a default input100
will be created within.Here is the details of running deploy script to testnet:
The
DeployFactory
contract 0x8c03eC86967347dEDB5f1614b0AB23e48F6a215D verify succeed, but theProxy
contract 0x22EA9D66eA20D0826444B9716Af4261Ce98b51Ba verify failed.The text was updated successfully, but these errors were encountered: