Deployed bytecode is not equal to the generated one from a given source

[lbeder]

Environment

Mainnet

Issue Type

• Plugin
• Block Explorer

Contract Address

0x21d8d4eE83b80bc0Cc0f2B7df3117Cf212d02901

Compiler Type

Multi-part contract

zkSolc Version

1.4.1

Solc Version

0.8.19

Contract Name

EAS

Contract Code

Please here: https://github.com/ethereum-attestation-service/eas-contracts/blob/zksync/contracts/EAS.sol

Constructor Arguments

Please here: https://github.com/ethereum-attestation-service/eas-contracts/blob/zksync/contracts/EAS.sol

Hardhat Verify Plugin Version

1.4.2

Repo Link (Optional)

https://github.com/ethereum-attestation-service/eas-contracts/tree/zksync

Additional Details

We deployed 4 EAS contracts, but the main EAS contracts cannot be verified. They deployed and complied, but only one contract cannot be verified (our main contract). We also tried verifying in the UI, but that didn't work either. Seems to be some syntax mismatch?

ErrorCode:
ZkSyncVerifyPluginError: Backend verification error: Deployed bytecode is not equal to the generated one from a given source

You can find the verification script here: https://github.com/ethereum-attestation-service/eas-contracts/blob/zksync/scripts/verify.ts, but please note that manual verification using the UX (using a flattened version) didn't work either.

Related branch of our deployment:
https://github.com/ethereum-attestation-service/eas-contracts/tree/zksync

[bxpana]

Any luck with verifying them via the Block Explorer? https://explorer.zksync.io/contracts/verify

Are any of the contracts you're trying to verify, deployed by another contract? There is a known issue with not being able to verify contracts deployed by other contracts right now.

[lbeder]

Any luck with verifying them via the Block Explorer? https://explorer.zksync.io/contracts/verify

Nope. It's exactly the same result when trying to verify via the Block Explorer. 3 contracts work well, and only one fails with the same error.

Are any of the contracts you're trying to verify, deployed by another contract? There is a known issue with not being able to verify contracts deployed by other contracts right now.

All the contracts are deployed using an EOA and exactly in the same way.

[bxpana]

Alright, will check on my end to see if I can replicate.

[lbeder]

Thanks 🙏

[nikola-bozin-txfusion]

Hey @lbeder , we've verified your contract: https://explorer.zksync.io/address/0x21d8d4eE83b80bc0Cc0f2B7df3117Cf212d02901#contract.
😄
We'll address the issue on the plugin side.

[lbeder]

Hey @nikola-bozin-txfusion, thanks for verifying, but have you noticed that you basically include all the contracts in the repo and not only the contracts used by EAS.sol? Could you please update it to only include the relevant contracts? Otherwise, it looks kind of looks weird and unprofessional :/

[nikola-bozin-txfusion]

When resolving contracts for verification of EAS Smart Contract, hardhat gathers dependent contracts.
It seems that is not enough for zksolc compiler (compilation output is different - bytecode) on BE for the verification, hence it fallsback to sending the the full source.
We will be working with the backend/compiler team to resolve this issue asap.

[lbeder]

Yeah, I completely understand why you have fallen back to an equivalent of etherscan''s --solc-input, but it currently makes the main contract appear bad. Please keep up posted when it's resolved so that we could reverify.

[lbeder]

Hey @nikola-bozin-txfusion, any news on this? Is it possible to properly re-verify the contracts?

[hedgar2017]

Already reported in the solc repo, but I've sent a link to this thread just in case:
ethereum/solidity#15134

[hedgar2017]

@lbeder according to the solc v0.8.26 release notes, a bug like that was fixed in 0.8.26, so I recommend trying that version when we release a zksolc with its support.

[lbeder]

Hi @hedgar2017, this isn't relevant to our issue.