Open mshakeg opened 8 months ago
The Greeter
contract was verified automatically as part of the deployment process, it would be great if libraries were also verified automatically as part of yarn hardhat deploy-zksync:libraries
Thanks for the information. We are aware of this issue and we are working together with the backend verification team to resolve it.
As for the automatically verifying libraries as part of yarn hardhat deploy-zksync:libraries
, that would mean that our deploy plugin needs to depend on verify plugin, and we don't want that because this would introduce unnecessary dependencies between those plugins.
Description
I am encountering an issue when attempting to verify a Solidity library on the zkSync network using the
@matterlabs/hardhat-zksync
plugin. While I was able to deploy a Solidity library (MathLib
) successfully, the verification process fails with an error indicating a bytecode mismatch. This issue seems specific to the verification of Solidity libraries, as I was able to verify a regular contract (Greeter
) without any problems.Steps to Reproduce
MathLib.sol
) and a dependent contract (Calculator.sol
).MathLib:
Calculator:
MathLib
library to the zkSync network:yarn hardhat deploy-zksync:libraries --private-key <private-key>
MathLib
library:yarn hardhat verify <MathLib address> --contract contracts/MathLib.sol:MathLib
. My library was deployed to0xE6f95768D5BADC7561EC7Fb6BCE2459F0fF69CDc