🐛 Bug Report
📝 Description
Contract verification fails on the zkSync Explorer UI when using multiple file contracts
🔄 Reproduction Steps
- Prepare a smart contract that uses imports and spans across multiple Solidity files
- Try verifying the contract using the zkSync Explorer UI
- Verification fails with the error:
Deployed bytecode is not equal to generated one
🤔 Expected Behavior
The contract should verify successfully if the correct constructor arguments and compiler settings are used, just like it does when verified using Hardhat
😯 Current Behavior
Verification fails on the UI for multiple file contracts, but works when using Hardhat
For single file contracts, both UI and Hardhat verification succeed
🐛 Bug Report
📝 Description
Contract verification fails on the zkSync Explorer UI when using multiple file contracts
🔄 Reproduction Steps
Deployed bytecode is not equal to generated one🤔 Expected Behavior
The contract should verify successfully if the correct constructor arguments and compiler settings are used, just like it does when verified using Hardhat
😯 Current Behavior
Verification fails on the UI for multiple file contracts, but works when using Hardhat
For single file contracts, both UI and Hardhat verification succeed