# How to verify a contract deployed using Remix importing OpenZeppelin via GitHub? **URL:** \ **Category:** Contracts\ **Created:** [March 4, 2020, 9:32pm UTC](https://forum.openzeppelin.com/t/how-to-verify-a-contract-deployed-using-remix-importing-openzeppelin-via-github/2413 "2020-03-04T21:32:39Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![x5engine](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.openzeppelin.com/x5engine/32/1834_2.png) [@x5engine](https://forum.openzeppelin.com/u/x5engine)\ **Post date:** [March 5, 2020, 1:59am UTC](https://forum.openzeppelin.com/t/how-to-verify-a-contract-deployed-using-remix-importing-openzeppelin-via-github/2413/2 "2020-03-05T01:59:03Z")
I have compiled and deployed the contract on remix with the flattener plug-in enabled, Then I have flattened the code for verification on etherscan which gives us these errors > **[Thanks a whole lot for this tutorial, I’ve been able to create a token but is...](https://medium.com/@petertmohan/thanks-a-whole-lot-for-this-tutorial-ive-been-able-to-create-a-token-but-is-yet-to-be-verified-a7529cf2543a)** > > Error! Unable to generate Contract ByteCode and ABI > Found the following ContractName(s) in source code : ApproveAndCallFallBack… As suggested by you to flatten the contract when you have imports (even importa from GitHub of zeplin). Then we did that but seems etherscan doesn’t know which contract bytes to compare to when you have a single file and many contracts defined in it… So you can reproduce this if you make a simple token erc721 or erc20 and import all it’s dependencies from GitHub deploy on remix then flatten it and try to verify it… Thanks --- _[View the full topic](https://forum.openzeppelin.com/t/how-to-verify-a-contract-deployed-using-remix-importing-openzeppelin-via-github/2413)._