Hi. I have deployed my contracts on Ropsten, created an instance of each and did
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.
Looking at “internal transactions” at https://ropsten.etherscan.io/address/0xc7db35F95af0eaD09f556305e28affB12cB2FA1E#internaltx gives some initial minting-operations on my token contract.
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:
It lists the token address with its proper name as: https://ropsten.etherscan.io/token/0x84e62624c28bf55b1dcc70b0c957b0e8479a20b7
But there is no contract code available and “read contract” and “write contract” aren’t any useful:
“Sorry, we were unable to locate a matching Contract ABI or SourceCode for this contract.”
I have to verify the code here again. Can we make
zos verify working that etherscan.io can properly handle it? Or did I miss something here?