Kaan Uzdoğan
Kaan Uzdoğan
Can you also provide test contracts for each network (with source code and metadata)? They can be easily deployed via the deploy script as described in [docs](https://docs.sourcify.dev/docs/chain-support/) but since these...
Asking for context: Is this for updating the IPFS hash under the ENS name?
Hello @arwer13 Yes, correct. However, we check against the deployed bytecode which does not contain constructor arguments information. This is only found in the contract creation transaction and not in...
Reopening, close once confirmed on CircleCI
My thinking was for such a file there would be one metadata output but yeah there are two different metadata.json's for two contracts linking to the same source file hash....
@JanRuettinger It is currently stale but we appreciate contributions. Are you familiar with the trace methods? The first steps would be what @chriseth mentioned above because we need to scan...
Hello @tjayrush It sounds super interesting. I'd be happy to learn more. Could you react me at [email protected]?
Hi. You need to provide those sources yourself if they are not published on IPFS. AFAIK there's no functionality in hardhat/truffle to publish a file on ipfs, but you can...
Could you maybe explain more about how it does not fit your workflow? What would be the ideal case for you? I'd be interested to know
This is the perfect place to discuss so thanks for the input :+1: . The verified contracts are kept in a file repository and not in a database. So the...