Support for contracts deployed via a factory? about truffle-plugin-verify HOT 7 CLOSED

At least proxies are supported now by Etherscan: https://medium.com/etherscan-blog/and-finally-proxy-contract-support-on-etherscan-693e3da0714b.

from truffle-plugin-verify.

thanks to PR #61 from @hellwolf it's now possible to provide the encoded constructor args as a force override with the --forceConstructorArgs option. I'll leave this issue open though since we might want to update this in the future to allow unencoded args or to figure out some automated process.

from truffle-plugin-verify.

Have you been able to verify these contracts manually through Etherscan? If so, what were the steps you took?

from truffle-plugin-verify.

My latest info is that it's not yet supported by Etherscan, see https://www.reddit.com/r/etherscan/comments/9uzw8i/eip1167_clonefactory_support/.

from truffle-plugin-verify.

are there any plans to fix this ? as suggested on another thread can we add a CLI argument with ctor params? that would help

from truffle-plugin-verify.

I'll x-post the reply from #35 here as well:

To respond to the issue: there's not a very easy solution yet. I'm considering to add a flag to the CLI to manually provide constructor parameters so it doesn't need to retrieve them from Etherscan. An alternative solution is to potentially use the Truffle Debugger to see if we can trace back the constructor parameters that were used. But for now unfortunately there's no good workaround.

Probably the easiest thing would be add a CLI flag --args that takes in (preferably the unencoded) args, which then get ABI encoded and are used by the plugin instead of trying to retrieve it from Etherscan. I'm open to any PRs that add this functionality.

from truffle-plugin-verify.

Since Truffle is being sunset, I don't plan to add new features, so I'm closing this issue. The "manual" constructor arg passing will have to do.

from truffle-plugin-verify.