Cainuriel:
Contract on Rinkeby: 0xa43C6f38Fd8b2F4462F52462dd20fA95597e3c1b
Ok,
Until now I had always compiled and verified from remix, this may be the problem.
Is there a tutorial here for hardhat verification?
The mechanism is the same for contracts in Binance Smart Chain since this network does not use API nodes?
I context myself because I have found the tutorials for hardhat. Before continuing to bother, I document better .. thank you very much for your time @Skyge
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…
1 Like