Hi,
as suggested read the topic:
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…
Tried to verify contracts on ropsten and mainnet and they fail:
truffle run verify NNNToken --network ropsten
or
truffle run verify NNNToken --network mainnet
all the code and configuration can be found here:
https://github.com/overqint/erc20_nnn
This is the deployed contract:
Novem Gold Token (NNN) Token Tracker on Etherscan shows the price of the Token $0.00, total supply 0, number of holders 0 and updated information of the token. The token tracker page also shows the analytics and historical data.
If we click on the contract address the proxy contract is verified:
Contract Source Code Verified (Similar Match)
The Contract Address 0x4cdbd3d80036a05a3162d492287a0960dce4a385 page allows users to view the source code, transactions, balances, and analytics for the contract address. Users can also interact and make transactions to the contract directly on...
Also tried to verify it manually, more info here:
Hello,
Deployed out upgradable Token Contract with a Proxy on the Mainnet
Contract code is here: https://github.com/overqint/erc20_nnn
unfortunately I got an error at the end of the deployment and and the artifacts are not created/saved.
[Screenshot 2020-12-11 at 10.11.28]
I can not interact with the token over the truffle console: NNNToken has not been deployed to detected network (network/artifact mismatch)
Is there a way to create the artifacts “manually”
As @abcoathup mentioned it …
And tried also this, with no success:
How can we also verify the NNNToken Contract?
1 Like
Hi @intoverq ,
I verified your implementation contract on mainnet using the following method: Verify smart contract inheriting from OpenZeppelin Contracts
I modified your imports in EnhancedMinterPauser
to not be relative:
import "@openzeppelin/contracts-upgradeable/presets/ERC20PresetMinterPauserUpgradeable.sol";
import "@openzeppelin/contracts-upgradeable/math/SafeMathUpgradeable.sol";
Using Hardhat Etherscan plugin I was able to verify
$ npx hardhat verify --network mainnet 0x8f8350fd36b1da9cc1e92744c8d8186ae0215d3c
Nothing to compile
Successfully submitted source code for contract
contracts/NNNToken.sol:NNNToken at 0x8f8350fd36b1da9cc1e92744c8d8186ae0215d3c
for verification on etherscan. Waiting for verification result...
Successfully verified contract on etherscan
On Etherscan, I then marked your proxy as a proxy, and as the implementation contract was now verified, you can now interact with your upgradeable contract via the proxy on Etherscan.
The Contract Address 0x4cdbd3d80036a05a3162d492287a0960dce4a385 page allows users to view the source code, transactions, balances, and analytics for the contract address. Users can also interact and make transactions to the contract directly on...
As an aside, your mainnet.json
file isn’t under version control. I recommend including this, see the documentation for details: https://docs.openzeppelin.com/upgrades-plugins/1.x/network-files#configuration-files-in-version-control
1 Like
Thank you very much @abcoathup for your help and a happy new year.
Uploaded also mainnet.json to github as suggested
1 Like