Upgradeable ERC20 token

[megatower66]

@abcoathup I found this tutorial Upgrade Token to include partial burn on transfer

Moved from: ERC20Detailed.sol not found in @openzeppelin/contracts/token/ERC20 on GitHub

[abcoathup]

Hi @megatower66,

Please note: we’ve decided it’s best to focus our upgradeability efforts on the Upgrades Plugins exclusively, and have halted development on the OpenZeppelin CLI. For details see:
Building for interoperability: why we’re focusing on Upgrades Plugins

I suggest looking at the following guides/tutorials to use Upgrades Plugins:

• Learn guides on Upgrading Smart Contracts: https://docs.openzeppelin.com/learn/upgrading-smart-contracts
• OpenZeppelin Upgrades: Step by Step Tutorial for Truffle

Also see: The Future of contracts-ethereum-package

[abcoathup]

Hi @megatower66,

Let me know if you need more information.

[megatower66]

Hi @abcoathup, that's helpful! Based on this, I actually wanted to see if you've solution to this issue:

Using AccessControl with ERC20 token (UpgradeSafe) throwing "Defining structs like `RoleData` is not yet supported"

As per @abcoathup’s suggestion to use OpenZeppelin ERC20 implementation, am creating a very simple upgradable ERC20 token as below: // contracts/MyToken.sol // SPDX-License-Identifier: MIT pragma solidity ^0.6.0; import "@openzeppelin/contracts-ethereum-package/contracts/token/ERC20/ERC20.sol"; import "@openzeppelin/contracts-ethereum-package/contracts/access/AccessControl.sol"; contract MyToken is Initializable, ERC20UpgradeSafe, AccessControlUpgradeSafe { bytes32 public constant B…

Thanks!

[abcoathup]

Hi @megatower66,

I have responded in that topic.