Help Verifying ERC20 Contract

[Patupai]

Hi there,

I am in need of help verifying a simple ERC20 contract deployed in remix. I have followed these tutorials:

How to verify a contract on Etherscan/BscScan/PolygonScan

Make sure to read this post before asking a question about verification. If your issue is not addressed here, just leave a comment below. If you want to pay someone to do the verification for you, create a post in Developer Wanted. This guide applies to all Etherscan instances, including all of the following as well as their testnet explorers: etherscan.io (Ethereum) bscscan.com (Binance Smart Chain) polygonscan.com (Polygon) snowtrace.io (Avalanche) Recommendations Practice in testnet Be…

Verify ERC20 token on Etherscan that was deployed through Remix: Step by Step Guide

At the previous tutorial: Create an ERC20 using Remix, without writing Solidity, we have learned how to deploy contracts with the Remix, and now in this tutorial, we will learn how to verify the deployed contracts by a single file. Cause many people deploy contracts by the Remix, so in this part, we will use the plugin FLATTENER in the Remix to help us to package all contracts file into a single file to verify. In short, all steps are: Compile contract Flatten contract Copy the whole code to…

And still have no solution.

Here is the error when compiling the flattened contract, with repo version specified...

Compiler debug log:
 Error! Unable to generate Contract Bytecode and ABI
 Found the following ContractName(s) in source code : Context, ECDSA, EIP712, ERC20, ERC20Burnable, ERC20Permit, IERC1155Errors, IERC20, IERC20Errors, IERC20Metadata, IERC20Permit, IERC5267, IERC721Errors, Math, MessageHashUtils, MyToken, Nonces, Ownable, ShortStrings, SignedMath, StorageSlot, Strings
 But we were unable to locate a matching bytecode (err_code_2)
 For troubleshooting, you can try compiling your source code with the Remix - Solidity IDE and check for exceptions


Compiler Version: v0.8.20+commit.a1b79de6
Optimization Enabled: True
Runs: 200
Bytecode (what we are looking for):
61016060405<<<shortened>>>

- vs what we got -

We tried looking for a match from the list of compiled contract bytecode outputs (as listed below), but was unable to find an exact match.

1) ECDSA
60556032600b8282823980515f1a607314602657634e487b7160e01b5f525f60045260245ffd5b305f526<<<shortened>>>

2) Math
60556032600b8282823980515f1a607314602657634e487b7160e01b5f525f60045260245ffd5b305f52607381538281<<<shortened>>>

3) MessageHashUtils
60556032600b8282823980515f1a607314602657634e487b7160e01b5f525f60045260245ffd5b305f52607381538281f3fe730000000000000000000000000000000000000<<<shortened>>>

4) MyToken
61016060405234801562000011575f80fd5b50604051620015d6380380620015d6833981016040819052620000349162000292565b6040518060400160405280600781526020016626bcaa37b5b2b760c91b81525080604051806040016040528060018152602001603160f81b815250836040518060400160405280600781526020016626bcaa37b5b2b760c91b815250604051806040016040528060038152602001624d544b60e81b8152508160039081620000bd919062000361565b506004620000cc828262000361565b5050506001<<<shortened>>>

5) ShortStrings
60556032600b8282823980515f1a607314602657634e487b7160e01b5f525f60045260245ffd5b305f52607381538281<<<shortened>>>

6) SignedMath
60556032600b8282823980515f1a607314602657634e487b<<<shortened>>>

7) StorageSlot
60556032600b8282823980515f1a607314602657634e487b7<<<shortened>>>

8) Strings
60556032600b8282823980515f1a607314602657634e487b7160e01b5f525f60045260245ffd5b305f5260738153<<<shortened>>>

This is on the sepolia test network.

The contract address is:

0x2b9f6d02228b572e33b2A4cda06dcdC49e527d37

and the constructor arguments are:

00000000000000000000000001e0a771dc549744685d41f48ba590230240ada2

I did not use optimization.

I want to understand where I went wrong and how to correct it.

I have tried the tool in Remix to no success.

[denyo1986]

You say you did not use optimization but when you try to verify it you verify it as if optimization was enabled with 200 runs:

Try to adjust that setting, disable optimization. Then try again.

[warrior_dragon]

Hello
@Patupai
I can help you to verify your smart contract.
If possible, could we discuss via Telegram?
TG name: @DesarrollaorTalentosa
I will wait for your reply.
Thanks.

[barakman]

This:

@Patupai

Optimization Enabled: True
Runs: 200

And this:

@Patupai

I did not use optimization.

Don't quite get along that well with each other.

In addition to that, you may need to reconsider this:

@Patupai

Compiler Version: v0.8.20+commit.a1b79de6

If you're using pragma solidity ^0.8.20 in your source code (which is what open-zeppelin are currently using in their source code), then at the time of writing this, you may have compiled your contract with any of the following versions:

• v0.8.20+commit.a1b79de6
• v0.8.21+commit.d9974bed
• v0.8.22+commit.4fc1097e
• v0.8.23+commit.f704f362
• v0.8.24+commit.e11b9ed9

For your contract verification procedure to succeed, you need to find out exactly which compiler version you have used.

[Patupai]

Thankyou @warrior_dragon and @jack04 for offering to help and reaching out. I respect the hustle.

The advice from @denyo1986 and @barakman pointed me in the right direction, along with some Patrick Collins tutorials to the point where I no longer need help on this.

Thank you for your support.