hardhat-ignition

hardhat-ignition copied to clipboard

### Describe the feature When deploying an upgradeable contract using a proxy, the typical way to do it would look something like this: ``` const proxy = m.contract('Proxy') const implementation...

alcuadrado

### Describe the feature If users create similar patterns of `Future`s, they would naturally want to avoid that repetition, and that can be done using normal javascript functions. The only...

alcuadrado

### Describe the feature ## Problem In some situations, a user needs to express that a `Future` should only be executed after an `IgnitionModule` has been executed. We have already...

alcuadrado

### Describe the feature While using Hardhat Ignition modules with hardhat fixtures in tests, I'm facing a problem. When using hardhat network and repeatedly executing `hardhat test test/myTest.ts` I get...

samokander

### Describe the feature ### Problem Sometimes it's useful to have a human readable way of visualizing the "transaction log history" for a deployment. ### Solution In conversation with @alcuadrado...

tmigone

Ignition status command does not work with external artifacts deployed

1

### Version of Hardhat 2.22.8 ### What happened? Same setup as in NomicFoundation/hardhat#5659. I'm using ignition to deploy external artifacts. After successful deployment I ran `npx hardhat ignition status op-sepolia-1`...

sim31

How to deploy upgradeable contracts in conjunction with @openzeppelin/hardhat-upgrades?

2

How to deploy upgradeable contracts in conjunction with @openzeppelin/hardhat-upgrades?

bentong-chain