# I can't verify my contract on BSCScan

**URL:** <https://forum.openzeppelin.com/t/i-cant-verify-my-contract-on-bscscan/8418>\
**Category:** Contracts\
**Tags:** erc20, etherscan-verify\
**Created:** [May 15, 2021, 3:24am UTC](https://forum.openzeppelin.com/t/i-cant-verify-my-contract-on-bscscan/8418 "2021-05-15T03:24:43Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lemon\_Juice](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.openzeppelin.com/lemon_juice/32/5759_2.png) [@Lemon\_Juice](https://forum.openzeppelin.com/u/Lemon_Juice)\
**Post date:** [May 15, 2021, 3:24am UTC](https://forum.openzeppelin.com/t/i-cant-verify-my-contract-on-bscscan/8418/1 "2021-05-15T03:24:43Z")

</div>

I have had some issues verifying my contract on BSCscan. I’m relatively new to this.

**Here is my code followed by the error:**

pragma solidity ^0.8.0;

import “[https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/token/ERC20/ERC20.sol](https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/token/ERC20/ERC20.sol)”;

contract CaribCoin is ERC20 {  
constructor(uint256 initialSupply) public ERC20(“CaribCoin”, “CARIB”) {  
\_mint(msg.sender, initialSupply);  
}  
}

Warning: SPDX license identifier not provided in source file. Before publishing, consider adding a comment containing "SPDX-License-Identifier: " to each source file. Use “SPDX-License-Identifier: UNLICENSED” for non-open-source code.

ParserError: Source “(previous link posted above. Cannot post more than 2 links due to new account)” not found: File import callback not supported  
 → myc:3:1:  
|  
3 | import “[https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/token/ERC20/ERC20.sol](https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/token/ERC20/ERC20.sol)”  
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

My contract adress:

0x980e479b9ddce4ee9ab5a7335fc5af1b8b91e616

---

<div class="post-metadata">

**Author:** ![Yoshiko](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.openzeppelin.com/yoshiko/32/6858_2.png) [@Yoshiko](https://forum.openzeppelin.com/u/Yoshiko)\
**Post date:** [May 15, 2021, 5:17am UTC](https://forum.openzeppelin.com/t/i-cant-verify-my-contract-on-bscscan/8418/2 "2021-05-15T05:17:56Z")

</div>

Hi @Lemon_Juice welcome to the Open Zeppelin forums.

Please follow the tutorial at [OpenZeppelin Upgrades: Step by Step Tutorial for Hardhat](https://forum.openzeppelin.com/t/openzeppelin-upgrades-step-by-step-tutorial-for-hardhat/3580) to get started.

Your verification problem is likely an environment issue.

Are you using Remix, Hardhat, or Truffle?

---

<div class="post-metadata">

**Author:** ![Lemon\_Juice](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.openzeppelin.com/lemon_juice/32/5759_2.png) [@Lemon\_Juice](https://forum.openzeppelin.com/u/Lemon_Juice)\
**Post date:** [May 15, 2021, 2:12pm UTC](https://forum.openzeppelin.com/t/i-cant-verify-my-contract-on-bscscan/8418/3 "2021-05-15T14:12:33Z")

</div>

I'm using Remix. I looked at this older threat where an identical issue to mine was resolved.

> [@Can't verify contract on BSC scan](https://forum.openzeppelin.com/t/cant-verify-contract-on-bsc-scan/6672):
>
> Im not sure what im doing wrong but i cant verify my contract on BSC scan. This is my simple code and the error: pragma solidity ^0.8.0; // SPDX-License-Identifier: MIT import "https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/token/ERC20/ERC20.sol"; contract RandCoin is ERC20 { constructor(uint256 initialSupply) public ERC20 ("RandCoin", "RAND") { \_mint (msg.sender, initialSupply); } } Compiler Warning(s): ParserError: Source not found: File impo…

Despite this, I can't seem to fix the problem.

---

<div class="post-metadata">

**Author:** ![Skyge](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.openzeppelin.com/skyge/32/343_2.png) [@Skyge](https://forum.openzeppelin.com/u/Skyge)\
**Post date:** [May 16, 2021, 1:32am UTC](https://forum.openzeppelin.com/t/i-cant-verify-my-contract-on-bscscan/8418/4 "2021-05-16T01:32:51Z")

</div>

Hi, welcome! 👋

Sorry, I am not familiar with the BSC-Chain, maybe you should ask for help in their forum: [Home | Binance Chain Forum](https://community.binance.org/)

And they have a documentation about how to verify contracts, maybe you can have a look at it:

- [Truffle Verify - Binance Chain Docs](https://docs.binance.org/smart-chain/developer/deploy/truffle-verify.html)
- [HardHat Verify - Binance Chain Docs](https://docs.binance.org/smart-chain/developer/deploy/hardhat-verify.html)

And your contract has been verified.

---

<div class="post-metadata">

**Author:** ![budapest77](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.openzeppelin.com/budapest77/32/4205_2.png) [@budapest77](https://forum.openzeppelin.com/u/budapest77)\
**Post date:** [June 13, 2021, 8:03am UTC](https://forum.openzeppelin.com/t/i-cant-verify-my-contract-on-bscscan/8418/5 "2021-06-13T08:03:02Z")

</div>

I have the same problem too… Anyone find out the solution yet?!!

---

<div class="post-metadata">

**Author:** ![Yoshiko](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.openzeppelin.com/yoshiko/32/6858_2.png) [@Yoshiko](https://forum.openzeppelin.com/u/Yoshiko)\
**Post date:** [June 14, 2021, 1:13am UTC](https://forum.openzeppelin.com/t/i-cant-verify-my-contract-on-bscscan/8418/6 "2021-06-14T01:13:18Z")

</div>

> [@Verify ERC20 token on Etherscan that was deployed through Remix: Step by Step Guide](https://forum.openzeppelin.com/t/verify-erc20-token-on-etherscan-that-was-deployed-through-remix-step-by-step-guide/9051):
>
> At the previous tutorial: [Create an ERC20 using Remix, without writing Solidity](https://forum.openzeppelin.com/t/create-an-erc20-using-remix-without-writing-solidity/2908), 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…

try this. It's written by the guy above you
