John Kane

While NomicFoundation/hardhat-ignition#823 is a limitation (we don't have all the info needed for verification), this looks like a bug where we are making incorrect assumptions in the `status` command.

Hey, @bentong-chain, `@openzeppelin/hardhat-upgrades` is a separate plugin and approach to upgrading smart contracts. You can upgrade contracts using Ignition, see our [docs on upgradable contracts](https://hardhat.org/ignition/docs/guides/upgradeable-proxies). Are there particular use cases...

I have been able to reproduce this issue locally. In `hardhat.config.ts`: ```ts networks: { // ... sepolia: { type: "http", chainType: "l1", url: configVariable("SEPOLIA_RPC_URL"), accounts: [configVariable("SEPOLIA_PRIVATE_KEY")], }, // ... },...

We have added a development keystore to allow storing config variables without needing a password. If you try and use a config variable when in tests (e.g. connecting to a...

I am moving this to draft as I think it overlaps with the open zeppelin work I am doing. My plan is to look this over, then rebase my changes...

Improving the release process is an ongoing task and will go through many iterations. Our top priority should be two tasks: * re-adding the auto-creation of draft github releases (an...

Currently we are not supporting Windows on ARM. We have two underlying libraries that do not support Windows on ARM: * EDR * Solidity analyzer We are investigating turning on...

To give an update on this, EDR support for Windows on Arm is on our roadmap but is not just the configuration update we were hoping it was. You should...

No updates I am afraid. It is on our roadmap but we don't have a firm timeline.

> > [@schaable](https://github.com/schaable) I've gotten the solution. > > ``` > > etherscan: { > > enabled: false, > > }, > > blockscout: { > > enabled: true, >...