[Contract Verification] Details on how the verification process works

[wighawag]

Environment

Testnet

Issue Type

• Plugin
• Block Explorer

Contract Address

Not relevant

Compiler Type

Multi-part contract

zkSolc Version

latest

Solc Version

latest

Contract Name

Not relevant

Contract Code

any

Constructor Arguments

any

Hardhat Verify Plugin Version

No response

Repo Link (Optional)

No response

Additional Details

I have my own verification setup and would like to support zksync

Unfortunately your doc redirect to tools and do not offer an explanation of how the process can work

https://docs.zksync.io/build/tooling/hardhat/hardhat-zksync-verify.html#commands

I noticed that the artifact generated by zksolc provide a metadata output that differs from normal solc

What I am supposed to send to sourcify / etherscan / blockscout api ?

Any link to your source code would be great

Thanks

[bxpana]

do not offer an explanation of how the process can work

Do you mean show exactly how the contract is verified behind the scenes of the tools?

What I am supposed to send to sourcify / etherscan / blockscout api ?

Right now my understanding is that using the hardhat verify tool only supports verifying contracts on https://explorer.zksync.io/, but we have plans to extend that in the future to support https://era.zksync.network/ (Etherscan version).

[bxpana]

Here's the repo if that helps https://github.com/matter-labs/hardhat-zksync/tree/main/packages/hardhat-zksync-verify

[bxpana]

Did this get you what you needed?

[wighawag]

I guess I can work with that, but ideally the doc should explain all what is needed without needing to look at specific framework integration code

[dutterbutter]

@wighawag there is also this doc outlining contract verification: https://docs.zksync.io/build/tutorials/how-to/verify-contracts.html

[wighawag]

This is just a doc on how to use a tool to verify. it does not explain how your zksync explorer api work and what data format, etc,,... it expects

[gedithejedi]

try this: https://block-explorer-api.mainnet.zksync.io/docs#/Contract%20API/ApiController_verifyContractSourceCode

Its quite similar to normal etherscan api with some differences

[bxpana]

@wighawag did this help you for what you were looking for? ☝️

[wighawag]

Yes should help, but how is the order of the library defined ?

[gedithejedi]

if you submit everything as standart-json-input you should not need the library specifications at all. Or at least I dont when im doing mine. @wighawag