If you use full URL in import call then you get “import call not supported” when trying to verify contract in Etherscan. I haven’t found a solution yet, to this problem. any ideas?

Hi @dkim777 , I have verified: https://ropsten.etherscan.io/address/0xcef5bec5c75354dd3001256157d5ca86c4aa04a3#code Your contract was compiled with solc 0.5.17 (as per the bytecode). To flatten I imported OpenZeppelin Contracts v2.5.0 as this is the version you used on your import. The flattened …

Hi @dkim777 , Welcome to the community :wave: I haven’t had success verifying in Remix. Instead I create a flattened version locally, first converting the imports to npm and using truffle-flattener and then manually verify in Etherscan using the following process: How to verify a contract deploye…

Hi @dkim777 , Were you able to verify?

Thanks for checking in. So I flattened following code below (flattened file attached) And tried the flattened code on REMIX but got following error. on line 17 on flattened file where it starts with abstract “ParserError: Expected pragma, import directive or contrac/interface/library definition.…

Hi @dkim777 , You will need to include the contract in your post as attachments via email get removed.

Hi @dkim777 , You will have to come into the forum to post. Please also include the deployed contract address and the license to use (I will assume MIT).

Here is the contract I’ve deployed that I was trying to verify the code. [image] MetaSolar (SOL) Token Tracker | Etherscan MetaSolar (SOL) Token Tracker on Etherscan shows the price of the Token $0.0000, total supply 887,999,598, number of holders 3 and updated information of the token. …

Wow, thanks! looks like I have mixed up different versions. Couple questions. I’ve used truffle-flattener to do this, is there different tool? Does selecting different license has any affects on verifying code on Etherscan? Thanks, and let me try to replicate this myself I know I have a good r…

So, here my dilemma. The reason I used version 2.5 of openzeppelin was because it has ERC20Detailed where it accepts third argument of decimal I wanted to change to 2. if I use latest, ERC20Detailed is missing and I would have to modify the ERC20.sol to specify my decimal. So here is what I did t…

Hi @dkim777 , When verifying we need to use the exact version of OpenZeppelin Contracts that we deployed, as otherwise there could be changes in the smart contract code. I used truffle-flattener to flatten the contract. License doesn't impact verification, but we need to make sure that we set the …

Verify contract importing OpenZeppelin via GitHub on Remix

Support Contracts

Topic		Replies	Views
Deployed Preset ERC20 using Remix and can't verify Contracts	6	6104	October 2, 2021
How to verify a contract on Etherscan/BscScan/PolygonScan Guides and Tutorials hide-post-links , etherscan-verify	73	62799	June 18, 2025
Use Truffle Flattener on Windows with OpenZeppelin Contracts 2.x Contracts	11	7437	October 26, 2020
Error! Verified Contracts OpenZeppelin Contracts etherscan-verify	17	2802	January 25, 2022
BSCscan - Unable to generate Contract ByteCode and ABI Support erc20 , openzeppelin-contracts	10	12740	August 5, 2022

Verify contract importing OpenZeppelin via GitHub on Remix

Related topics