John Kane

Results 281 issues of John Kane

Integrate with `hardhat-ledger` to allow Ignition deployments to leverage a ledger hardware wallet. There are several issues that create friction between Ignition and `hardhat-ledger`: 1. hardhat ledger exposes ledger accounts...

type:epic

We export artifacts based on the future id, which includes the `#` symbol as a separator: ![image](https://github.com/NomicFoundation/hardhat-ignition/assets/24030/b30ae2dd-ff5e-4af2-ad71-1c47d6bd0216) When imported via vite it fails to resolve the import: ``` [vite] Internal...

status:needs-decision

For version management and releases switch to [changesets](https://github.com/changesets/changesets). This will bring us into line with Hardhat. It has the downside of having to switch away from the more expressive [Keep...

type:chore
status:ready

Reported on discord: https://discord.com/channels/750408878008827925/1153426756901032037/1212377098526924900 Building a subgraph requires knowing when to start indexing based on block number. It should be possible to retrieve the block numbers of the successful transactions...

status:ready
type:feature

We currently support `create2` through the [createX contract factory](https://github.com/pcaversaccio/createx). createX provides `create3` support but this is not currently exposed in Hardhat Ignition. Rather than alter the existing `create2` support we...

status:ready

> NOTE: this is a placeholder issue for organizing subissues We want to enable larger projects to extend **Hardhat Ignition** with custom execution logic that we have not thought of,...

type:epic

Execution engine takes a execution strategy. This should be exposed through deploy, with a default of the basic strategy. For consideration, do we need a reconcile step for strategy? This...

type:chore
status:ready

The deploy command should make the modulePath parameter optional. If the user has a `main.js/ts` module in their modules folder this will be used instead.

status:ready
type:improvement

This is a placeholder for the different improvements we want to make to the cli experience, particularly in showing progress during deploy. ## Subtasks - [x] #586 - [x] #587...

type:epic
status:ready

We should make our deployment artifacts lighter and friendlier for version control. There are two things obvious paths forward here: 1) Make the BuildInfo files lighter. This can be done...

type:epic
status:ready