El De-dog-lo

Created: https://github.com/ethpm/ethpm-rs

so, `Contract` excepts either a `contract_type=...` or an `abi=...` kwarg, which should bypass calling out to etherscan in order to fetch the contract type. further, if you have already downloaded...

> we could do something else too like adding `-f import_graph` as a compiler output option or something, i'm open to suggestions. Having the import graph would be extremely useful,...

> @fubuloubu also check `-f annotated_ast` output, it contains information about the imported modules including the sha256sum of the content. you can use this to compute a reproducible import graph....

> Let's see if this is even a problem first as well. This is still in development, but getting closer each day. If we can handle Solidity, I think we...

> one thing i can do (and i was thinking about doing this anyway) is to move the compiler's import analysis into an even earlier phase, so basically the only...

> > we essentially do import analysis to build the graph of the project, so this would be really nice to expose. we may in the future execute multiple compiler...

Any updates on this? Note that in the past few months we added support for separated contract type json files to better support external tooling It should be similar to...

Had an idea that an evmole ExplorerAPI plugin might be cool, or at least after the major refactor we want to do with the contract system where it becomes a...

Yes, I think it's important to have this functionality in Core, and my concerns with cookiecutter are no longer an issue as they are more actively developed now