Cannot transfer tokens from contract to wallet

[abcoathup]

Hi @DuckSoldier,

Welcome to the community

To use OpenZeppelin Contracts you should import the contracts. In Remix you can import via GitHub.

To keep your system secure, you should always use the installed code as-is, and neither copy-paste it from online sources, nor modify it yourself.

See the ERC20 example using OpenZeppelin Contracts 2.5:

Deploy a simple ERC20 token in Remix

I have been using Remix for really quick contracts rather than spinning up a Truffle or a Hardhat project (both of which are still pretty quick to do). Remix supports importing via GitHub. See the documentation for details: https://remix-ide.readthedocs.io/en/latest/import.html This makes it easy to import OpenZeppelin Contracts. Note: You should only use code published in an official release of OpenZeppelin Contracts, the latest release is 3.4. When importing via GitHub on Remix …

Also see Remix documentation for importing via GitHub:
https://remix-ide.readthedocs.io/en/latest/import.html#importing-from-github

The contracts in the OpenZeppelin Contracts repository master branch are part of the upcoming OpenZeppelin Contracts 3.0 (currently at OpenZeppelin Contracts v3.0 final release candidate) and use Solidity 0.6.

I have a simple ERC777 token (using OpenZeppelin 2.5) which can be deployed using OpenZeppelin CLI or Truffle (I would need to put together an example that works in Remix):

Simple ERC777 token example

OpenZeppelin 2.3.0 release candidate includes an implementation of ERC777. I created a simple ERC777 token inheriting from the OpenZeppelin implementation, based on the SimpleToken example. A key point to note is that in a testing environment an ERC777 token requires deploying an ERC1820 registry using @openzeppelin/test-helpers. (Thanks @frangio) The same applies when deploying to a private network. (We can use the OpenZeppelin Test Helpers to deploy the ERC1820 registry to a private network…