[Contract Verification] Factory automatic verification

[nfts2me]

Environment

Mainnet

Issue Type

• Plugin
• Block Explorer

Contract Address

Factory

Additional Details

I have a contract factory which creates new contracts using their bytecode hash to create them.

How to get those contracts created with the factory automatically verified?
All of them share the same source code, it would make sense to verify all of them with the same bytecode automatically despite having different addresses and constructor arguments.

[idea404]

A suggestion would be to have a machine monitor whenever the factory deploys a new contract and then programatically perform the verification. Not the neatest setup but I do not think you can upload a script to the explorer that would perform this step for you whenever the factory deploys a contract.

As for standard functionality in the explorer, the team is exploring ways to support this in future once the verification functionality has been implemented to the app.

[nfts2me]

On other explorers from other EVMs, proxies are automatically verified with the source of the destination contract.
Here, it would be even more straightforward, as the code is the same for all the contracts.
All the contracts with the same sourcecode should be automatically verified from the zkSync explorer.

[nfts2me]

What's that?
I've never heard of a "contract verification service" on zkSync, just this: https://docs.zksync.io/build/tooling/block-explorer/contract-verification.html

[nfts2me]

OK, I see. Just a IA bot response farming. Please, any @admin remove this.

[nfts2me]

Another IA bot response farming. Please, any @admin remove this.

[nfts2me]

Another IA bot response farming. Please, any @admin remove this.

[AlbionaHoti]

Hi @nfts2me,

It's been a long time, but I just wanted to share that now we have Etherscan support for the zkSync Era network; please find the link here, and you will be able to verify factory SC automatically there.

[nfts2me]

Thank you @AlbionaHoti , but unfortunately it is not working.

Last time we checked (a few days ago) latest zksolc was not supported, and hardhat-verify method was not working either.
But not only that, trying on an older version, there were only error, it didn't compile using the UI.

Do you know anyone from the team to talk via Telegram or other way to try to solve it?

[bxpana]

What version of Solidity is your factory in? When you say they aren't working what errors are you seeing?

[nfts2me]

solidity 0.8.24
zksolc 1.4 (which is over a month old)

Right now, for instance, the latest 0.8.5 solidity compiler is shown, but not the latest zksold version.

Error when trying using the latest version through the UI (tried with 1.3.22 compiled contract).

Compiler debug log:
 Error! Unable to generate Contract Bytecode and ABI (General Exception, unable to get compiled [bytecode])
 For troubleshooting, you can try compiling your source code with the Remix - Solidity IDE and check for exceptions

I also haven't been able to verify using hardhat-verify plugin for the era.zksync.network explorer.

[bxpana]

Apologies for the delay here, catching up after being out sick. I'll report back to the team and see what's up.

You're not able to verify using our explorer, https://explorer.zksync.io/ either correct?

[nfts2me]

Another farmer bot...

[nfts2me]

The problem with that explorer is that we use a contract factory. And contracts are created using create2 from the bytecodehash. So we cannot verify all of them individually as we are a permissionless protocol.

…

On Wed, 10 Apr 2024 at 02:48, bxpana ***@***.***> wrote: Apologies for the delay here, catching up after being out sick. I'll report back to the team and see what's up. You're not able to verify using our explorer, https://explorer.zksync.io/ either correct? — Reply to this email directly, view it on GitHub <#72 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2ENDR5R6PJB2GCZK32KNOLY4SD7RAVCNFSM6AAAAAA2UNQZ66VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TANRUHA3DO> . You are receiving this because you were mentioned.Message ID: <zkSync-Community-Hub/zksync-developers/repo-discussions/72/comments/9064867 @github.com>

[bxpana]

Ok let me look into this

[bxpana]

So it looks like this is currently a known issue of not being able to verify contracts that have been deployed from another contract. It's something we have planned to implement in the future though. Is that a blocker for you guys right now?

[nfts2me]

Rather than a blocker, it is a complain from the users that are unable to see their contracts verified.

[bxpana]

Understood. We apologize for the inconvenience, but will keep the community updated on when we have that feature available.

[gedithejedi]

@bxpana any update on this?

[bxpana]

@gedithejedi no update on this and will probably be a bit before we have this as an option.