Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Support for contracts deployed via a factory?

See original GitHub issue

Hello! Thanks for your work on this! This is very exciting for us!

That said, we have a challenge because the contract we’d like to verify (this one for example) is deployed via another contract.

It looks like this causes 2 different issues:

It needs an address inside of the PublicLock.json. This is one is easy, I just manually updated the json file to add one of an existing deployed contract
It needs to find the input field on the transaction which instantiated the contract. This one is trickier, because that transaction was not tiggered by me and since this is an “internal” transaction we do not get to access the input field.

Any way you could support the factories?

Issue Analytics

State:
Created 4 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

rkaliscommented, May 7, 2021

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.

1reaction

gorgoscommented, May 1, 2020

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