John Kane

You can't compute over the value of a future. We do want to support complex use cases though, to help me understand, the intent here is to allow `calldata` to...

We prioritized Etherscan based on usage, but we should provide this as an option to Ignition verification. If you are keen on this feature, please give a thumbs up!

> @kanej any update how v3 is progressing and this gets supported? It is progressing well. Work on the enhanced build system, including better support for verification is being worked...

We are tackling this with the beta follow on work. We will do it as part of the `create2` work. Adding strategy to the signature, adds the entirety of our...

I suspect we should export a new type that can be used in this situation, so you would set the return of the helper function to something like: `ViemIgnitionResultFor` rather...

We have a POC for create2 support. Our plan is to tackle this as: - get `create2` support out as another internal strategy - follow on with public strategies api

Thanks @ac-cb, Ignition doesn't currently support deploying vyper contracts. I have change the title of this issue to reflect that more general issue so that people can comment or plus...

@zoeyTM if I am following. During validation we add additional checks to args (either call or constructor) that recursively cross checks the types of the passed values with the ABI's...

The intention here is revisit our module parameter file usage in the run into HH v3.

Can I clarify, is it in the module file that you are wanting to pass values into the module definition that have been loaded asynchronously? So: ```shell ./ignition/modules/LockModule.js ``` As...