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 it also possible over etherscan or programmatically with web3js to interact with the contracts
but would be easier at the moment to interact with the truffle console.
Another important question is:
If we decide to upgrade the contract will this failed deployment have an effect and would cause problems?
The main problem is also that I am not able to verify the contract on etherscan; what I have tried so far:
Created Constructor Parameters here:
Argument 1 String: Novem Gold Token
Argument 2 String: NNN
Thanks I have read the article, it’s very similar to truffle upgrade, I have managed to test and deploy upgrades locally, please see my question, would be a update further down the road a problem if artifacts or or something else is missing (about truffles deploy process) that I’m not aware of and would make problem during the update process?
Your upgradeable contract seems to have deployed correctly. The problem may be just that Truffle didn’t store the address in the artifact file because the migrations failed. This would be the source of the “has not been deployed” error.
The address is stored in the networks field of the JSON artifact. It would look something like this:
"networks": {
"<network id>": {
"events": {},
"links": {},
"address": "<contract address>" // this would be the proxy address
}
},
You could try to add this entry in manually, but I’m not familiar enough with Truffle to understand if this would be a problem.
You can also just use your contract through the Truffle console by using:
new NNNToken(/* proxy address */)
instead of NNNToken.deployed().
As for problems with upgrades in the future, due to the half-failed migrations: it may have happened that your migration contract didn’t update to reflect the last run migration, and so a subsequent truffle migrate command will re-run one of your current migrations, and if I’m not mistaken that would redeploy your contract.
I would recommend consulting Truffle about this particular situation and see if our assessment about the migrations potentiall rerunning is correct, and what can be done to remedy it.