Skip to content

[Contract Verification] Deployed bytecode is not equal to generated one from given source #538

Discussion options

You must be logged in to vote

It appears that the contract underwent changes between deployment and the verification, resulting in differing metadata (non-executable part of the bytecode). The ZkSync verifier backend is sensitive to these changes, unlike the behavior on Etherscan. On zkSync, only full verification is supported, not partial, at the moment.

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by bxpana
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contract-verification Questions for contract verification
2 participants