[Dev Tools] Hardhat zksync - Error verifying contract on abstract testnet

[coffeexcoin]

Team or Project

Abstract

Environment

Testnet

Select the Dev Tool you are using

Hardhat Plugins

Provide the version of the tool (if applicable)

No response

Provide a brief description of the functionality you're trying to implement and the issue you are running into.

Getting an error attempting to verify a contract I just deployed on abstract testnet:

Error in plugin @matterlabs/hardhat-zksync-verify: Backend verification error: Unknown zksolc version: v1.5.8

For more info run Hardhat with --show-stack-traces

Repo Link (Optional)

No response

Additional Details

No response

[gleenai[bot]]

It appears that the error you're encountering is due to the use of an unsupported version of zksolc in your Hardhat configuration. The @matterlabs/hardhat-zksync-verify plugin requires a specific version of zksolc that is compatible with the ZKsync network.

To resolve this issue, you should ensure that you are using a compatible version of zksolc. Typically, the latest version is recommended unless specified otherwise in the ZKsync documentation. You can update your zksolc version by modifying your Hardhat configuration file to match the supported version.

For more detailed guidance on setting up and configuring your Hardhat environment for ZKsync, including the correct versions of tools and plugins, please refer to the ZKsync Hardhat plugin documentation.

If you continue to experience issues, I recommend visiting the ZKsync developers discussions on Github for more in-depth support and troubleshooting.

Your feedback helps us serve you better. If this fully addresses your question, please give it a thumbs up. If it doesn't, please give it a thumbs down. This will inform the community and team so we can improve our support.

[dutterbutter]

Hey @coffeexcoin

I see the issue, let me see if I can quickly resolve as v1.5.8 was recently released which should have been picked up by the verifier.

[dutterbutter]

The issue has been resolved and is part of the next release here. Apologies for the inconvenience here, the provided fix adds further automation which should prevent this in the future.

[shahar4]

@coffeexcoin @dutterbutter this is solved now. We've updated the verifier to automatically poll new compilers as @dutterbutter mentioned above, so this will not recur.