[Contract Verification] Unable to verify on etherscan

[uF4No]

Environment

Mainnet

Block Explorer

https://era.zksync.network/

Issue Type

• Plugin
• Block Explorer

Contract Address

0x000000

Compiler Type

Single file

zkSolc Version

1.4.1

Solc Version

0.8.21

Contract Name

Greeter

Contract Code

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.17;

contract Greeter {
string private greeting;
bool private greetingChanged;
constructor(string memory _greeting) {
greeting = _greeting;
greetingChanged = false;
}
function greet() public view returns (string memory) {
return greeting;
}
function setGreeting(string memory _greeting) public {
require(bytes(_greeting).length > 0, "Greeting must not be empty");
greeting = _greeting;
greetingChanged = true;
}
function isGreetingChanged() public view returns (bool) {
return greetingChanged;
}
}

Constructor Arguments

hello

Hardhat Verify Plugin Version

No response

Repo Link (Optional)

No response

Additional Details

No response

[gleenai[bot]]

It appears you are trying to verify a contract on the zkSync Era network using the Etherscan block explorer, which is not compatible with zkSync Era. For verifying contracts on the zkSync Era network, you should use the appropriate tools and platforms that support zkSync Era's environment.

Here are the steps to verify your contract on the zkSync Era network:

1. Access the Contract Verification Page: Go to the Smart Contract Verification page on the zkSync Era block explorer.

2. Enter Contract Details:

   • Contract Address: Enter the contract address (0x000000 in your case).
   • Compiler Type: Select the compiler type used (Solidity in your case).
   • zkSolc Version: Select the zkSync Era compiler version for Solidity used in your code (1.4.1).
   • Solc Version: Specify the Solidity compiler version used in your code (0.8.21).

3. Provide the Contract Code: Input the contract code as you have provided in your query.

4. Constructor Arguments: Since your contract uses constructor arguments, you will need to provide the ABI-encoded constructor arguments. For the Greeter contract with the greeting "hello", you will need to encode this argument. You can use tools like ABI.hashex.org to generate the ABI-encoded arguments.

5. Submit for Verification: After filling in all the required fields, submit the form for verification.

If you encounter issues with the verification process, such as mismatches in bytecode due to compiler settings or the specific version of zkSolc not being supported, you may need to adjust your compiler settings or wait for updates in the zkSync Era's backend to support the latest compiler versions.

For further assistance or if you encounter specific errors during the verification process, please refer to the zkSync Era documentation on contract verification or reach out for support through the appropriate channels.

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.