Hello Community just read through another post about converting imports and verifying when using Github. I made the mistake of not compiling now I need to get this sorted. I tried what was in here however could not get it to verify: [image] How to verify a contract deployed using R…

Hi @wizard-deVv , I verified your contract doing the followng: Create a simple Truffle project, installed OpenZeppelin Contracts 3.2 and Truffle Flattener. Converted GitHub imports to npm imports on the contract Ran Truffle Flattener $ npx truffle-flattener ./contracts/creepsv2.sol > ./contracts/…

So you want to verify this contract: wizard-deVv/mythic-finance/blob/main/creepsv2.sol , right? What is your contract address?

Hey there, I am currently interacting using web 3 but would like it to be publicly verified but struggling to get it, will never use github imports again now that see how easy truffle is… [image] Mythic Creeps v2 (CREEPSv2) Token Tracker | BscScan Mythic Creeps v2 (CREEPSv2) Token Tracker…

Hi @wizard-deVv , Welcome to the community :wave: When converting to npm imports, you need to install the same version of OpenZeppelin Contracts. In your case you were importing OpenZeppelin Contracts 3.2 via GitHub so need to install npm install @openzepplin/contracts@3.2.0 Using Binance Smart C…

Thanks! Yes i did install the 3.2 Version, BSC is the exact same as ETH from my experience so far. Not sure why like i stated above after flattening and removing duplicate License I got a really weird error.

Bro make a new post why did you hijack mine?

Hi @wizard-deVv , Just wanted to check if you were able to verify?

No not yet, I tried all those things and unfortunately still getting the same errors

[image] abcoathup: Encoded your constructor arguments using https://abi.hashex.org/ Looks like this was the step i was missing here :slight_smile: Encoded your constructor arguments using https://abi.hashex.org/ You are a legend thank you for all you do here!

@abcoathup Hello! I am also having troubles trying to verify my smart contract for an ERC721 token. I deployed it on Remix and this is the error im getting, "Error! Unable to generate Contract ByteCode and ABI (General Exception, unable to get compiled [bytecode])" Do you know how this can be solv…

How to Verify Contract on Etherscan Using Github Imports Via Remix

Support Contracts

Topic		Replies	Views
How to verify a contract deployed using Remix importing OpenZeppelin via GitHub? Contracts	9	14218	September 18, 2021
Verify contract deployed with Remix Contracts	6	9293	December 31, 2020
Verify ERC20 token on Etherscan that was deployed through remix Support	5	1905	March 31, 2021
Need help to verify contract Contracts	5	4896	December 22, 2021
ERC721 Contract Cant Verify due to Source "@openzeppelin/contracts/token/ERC721/ERC721.sol" not found: File import callback not supported Contracts erc721 , etherscan-verify	3	758	July 23, 2024

How to Verify Contract on Etherscan Using Github Imports Via Remix

Related topics