How to verify multi-file ERC20 contract importing other files

[frangio]

@TokenBuildingNewbie

The problem stems from me downloading the OpenZeppelin library rather than importing from git as I wanted to change some things such as the decimals.

This is not how you're supposed to use the library. From the documentation:

The defaut value of decimals is 18. To select a different value for decimals you should overload it.

---

How have you deployed this contract? Did you use Remix or Hardhat. See these guides:

Verify ERC20 token on Etherscan that was deployed through Remix: Step by Step Guide

At the previous tutorial: Create an ERC20 using Remix, without writing Solidity, we have learned how to deploy contracts with the Remix, and now in this tutorial, we will learn how to verify the deployed contracts by a single file. Cause many people deploy contracts by the Remix, so in this part, we will use the plugin FLATTENER in the Remix to help us to package all contracts file into a single file to verify. In short, all steps are: Compile contract Flatten contract Copy the whole code to…

How to verify with Hardhat or Truffle a smart contract using OpenZeppelin Contracts

For a complete list of resources regarding verification visit How to verify a contract on Etherscan/BscScan/PolygonScan. The recommended way to verify a smart contract inheriting from OpenZeppelin Contracts is as a "multi-file" contract (corresponding to the Standard-Json-Input compiler type on Etherscan). It is easier to read, imports are maintained, licenses are maintained. Verified using Hardhat Verified using Truffle Hardhat Hardhat has an Etherscan plugin: Hardhat Etherscan plugin N…

---

PS: Please use triple backticks to surround your code in order to get proper formatting.

```
code here
```