Hi. I have deployed my contracts on Ropsten, created an instance of each and did zos verify.
However, while verification was successful, it is combined with a different address then the token finally has.
What I did:
$ zos verify --remote etherscan --network ropsten --api-key XXXXXXXXX
? Pick a contract NCDToken
? Was the optimizer enabled when you compiled your contracts? Yes
? Specify the optimizer runs 200
✓ Contract source code of NCDToken verified and published successfully. You can check it here: https://ropsten.etherscan.io/address/0xc7db35F95af0eaD09f556305e28affB12cB2FA1E#code
At the URL from the response listed above the contract code can be viewed. But it is not linked to the final contract code.
But, looking at these operations with a click on the transaction ID at etherscan.io will list another address for the token, where no contract-code is visible:
I’m curious if I should verify the contract then manually also for the Proxy contract as this is the final contract that people will see on etherscan.io following the transaction. What do you think?
You should be able to manually verify the Proxy contract, though assume you would want to provide a guide to the tokens users that the smart contract is upgradeable and where they can find the Proxy contract and the Logic contract.