# Verify contract deployed with Remix

**URL:** <https://forum.openzeppelin.com/t/verify-contract-deployed-with-remix/5229>\
**Category:** Contracts\
**Created:** [December 20, 2020, 8:08pm UTC](https://forum.openzeppelin.com/t/verify-contract-deployed-with-remix/5229 "2020-12-20T20:08:32Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![abcoathup](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.openzeppelin.com/abcoathup/32/415_2.png) [@abcoathup](https://forum.openzeppelin.com/u/abcoathup)\
**Post date:** [December 30, 2020, 3:34am UTC](https://forum.openzeppelin.com/t/verify-contract-deployed-with-remix/5229/4 "2020-12-30T03:34:07Z")

</div>

Hi @woody567890,

I use Hardhat to verify, after first converting GitHub imports to npm imports.

I recommend trying the following: [Verify smart contract inheriting from OpenZeppelin Contracts](https://forum.openzeppelin.com/t/verify-smart-contract-inheriting-from-openzeppelin-contracts/4119).

Using a single flat file means that licence and import information is removed and makes it harder to read.

* * *

⚠ When importing via GitHub, you should specify the release tag, otherwise you will get the latest code in the master branch. For OpenZeppelin Contracts you should only use code published in an official release. (see [Importing from GitHub](https://remix-ide.readthedocs.io/en/latest/import.html#importing-from-github) in the Remix documentation).

Importing from the master branch can cause issues with verifying as the code in the master branch can change over time.

---

_[View the full topic](https://forum.openzeppelin.com/t/verify-contract-deployed-with-remix/5229)._