Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Automatically verifiable contracts in etherscan #6200

Closed
rstormsf opened this issue Aug 1, 2017 · 3 comments
Closed

Automatically verifiable contracts in etherscan #6200

rstormsf opened this issue Aug 1, 2017 · 3 comments
Labels
Z1-question 🙋‍♀️ Issue is a question. Closer should answer.

Comments

@rstormsf
Copy link

rstormsf commented Aug 1, 2017

I'm curious how do you call etherscan API to make MultiSig contract already verifiable as soon as you create it ?
It only work in mainnet, it doesn't work in testnets.

Please let us know of this cool trick that you used there.

@5chdn 5chdn added the Z1-question 🙋‍♀️ Issue is a question. Closer should answer. label Aug 1, 2017
@5chdn
Copy link
Contributor

5chdn commented Aug 1, 2017

It matches the bytecode of deployed contracts. If there are exact matches (i.e., multiple instances of deployed multi-signature contracts), etherscan knows this contract is already existing. If some users verifies one of these deployed contracts, etherscan also knows this is the exact code used for all of the other contracts.

@5chdn 5chdn closed this as completed Aug 1, 2017
@rstormsf
Copy link
Author

rstormsf commented Aug 3, 2017

hmmm...why it is not the case when I deployed multisig with 1.6.10 ? I'm sure there are many multisig contracts that were deployed with 1.6.10 and etherscan doesn't know about them? Can't be true.
Also how does it know which Constructor params were passed in ?

@5chdn
Copy link
Contributor

5chdn commented Aug 3, 2017

It's because we recently updated our contracts and nobody verified it yet.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Z1-question 🙋‍♀️ Issue is a question. Closer should answer.
Projects
None yet
Development

No branches or pull requests

2 participants