# Online ERC20 contract verifier - Showcase

**URL:** <https://forum.openzeppelin.com/t/online-erc20-contract-verifier-showcase/1642>\
**Category:** Showcase\
**Created:** [October 28, 2019, 6:14am UTC](https://forum.openzeppelin.com/t/online-erc20-contract-verifier-showcase/1642 "2019-10-28T06:14:53Z")\
**Posts on this page:** 1\
**Page:** 1

<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:** [October 28, 2019, 6:14am UTC](https://forum.openzeppelin.com/t/online-erc20-contract-verifier-showcase/1642/1 "2019-10-28T06:14:53Z")

</div>

Adding [https://erc20-verifier.openzeppelin.com/](https://erc20-verifier.openzeppelin.com/) to the showcase.

> [@Online ERC20 contract verifier](https://forum.openzeppelin.com/t/online-erc20-contract-verifier/1575):
>
> Integrating ERC20 tokens in an app has usually been the source of unexpected issues, due to contracts not properly adhering to the standard. [Nacho Mazzara](https://twitter.com/nachomazzara) from Decentraland [wrote about this](https://decentraland.org/blog/technology/safe-erc20-transfers/) almost a year ago. And with DeFi composability on the rise in the past few months, these problems are surfacing more and more often. We heard a lot of complaints about this recently in Devcon as well. To help with this, we took a few hours off from our daily tasks and decided to repurpose a verifier tool b…