Having deployed our contracts to Rinkeby, we can now start telling the public about our token sale and wait for the investment to roll in. However, any conscientious investor would likely question the transparency of our deployments – how do they know our contracts can be trusted? As it stands, our contracts' bytecode can be viewed on EtherScan, but this isn't human-readable, and doesn't immediately help with convincing investors of our transparency.
One solution to this problem is to verify and publish our contract code on Etherscan, using the tool at https://rinkeby.etherscan.io/verifyContract. To do this, we require the following:
- The contract addresses, which can be found in the output of the deployment stage.
- The contract names, which we defined as PacktToken and PacktTokenSale.
- The compiler version used by Truffle...
