hardhat-ignition

hardhat-ignition copied to clipboard

`Retrieving transaction for interaction` hangs

6

Hi there, im having some trouble attempting to deploy on the Flow EVM. With verbose on, this is what i see ``` Hardhat Ignition 🚀 Resuming existing deployment from ./ignition/deployments/chain-646...

ianthpun

resolves #760

zoeyTM

```typescript m.encodeFunctionCall< ContractNameT extends string, FunctionNameT extends string >( contract: CallableContractFuture, functionName: FunctionNameT, args: ArgumentType[] ): EncodeFunctionCallFuture interface EncodeFunctionCallFuture< ContractNameT extends string, FunctionNameT extends string > { type: FutureType.ENCODE_FUNCTION_CALL; id:...

zoeyTM

To better target our resources we want to understand which chains are seeing the most Ignition deploys. We need to capture that as part of our analytics. ## TODO -...

kanej

zoeyTM

Add sample project for upgradeable proxy usage

1

resolves #641

zoeyTM

We put together a `hardhat-deploy` to Hardhat Ignition migration guide for our blog: https://blog.nomic.foundation/migrating-to-hardhat-ignition-from-hardhat-deploy-c17311bb658f We should add a version of it to our docs guide. I think we should add...

kanej

Unexpected all the transactions of its network interaction were dropped

22

When not getting #664, I got this new error, however one tx creating one of the contracts is being emitted properly (can see it in the explorer), and it get...

gionn

Ignition modules provide significant features (e.g. restartable deploys) but for the simplest case of deploying a single contract, it adds the boilerplate of declaring a module. Can we reduce/eliminate the...

kanej

Check the order of parameters in the constructor of a contract when using buildModule.

5

Sometimes a contract has multiple parameters in its constructor. It's easy to accidentally swap the order of these parameters. Does Hardhat Ignition currently offer the functionality to display parameter names,...

alicercedigital