[Contract Verification] Deployed bytecode is not equal to generated one from given source #538
-
EnvironmentTestnet Block ExplorerIssue Type
Contract Address0x1A9f79A1e796Cde08fBD39Da6ffFa3bCf6E27121 Compiler TypeMulti-part contract zkSolc Version1.4.1 Solc Version0.8.24 Contract NameAccount factory Contract Codehttps://github.com/zkemail/clave-contracts/blob/master/contracts/AccountFactory.sol Constructor Arguments0x0A306bA833C8E071F9363bB32465778BFf22E30c Hardhat Verify Plugin Version2.0.3 Repo Link (Optional)https://github.com/zkemail/clave-contracts Additional DetailsI have the problem for verifying contact on zksync sepolia. hardhat-zksync failed to verify on zksync sepolia when I try to deploy contracts. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
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. |
Beta Was this translation helpful? Give feedback.
-
@kiriyaga-txfusion Thank you for your investigation.
For example (this is another deployed contract from this repo by me) |
Beta Was this translation helpful? Give feedback.
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.