Ch3 Extension hardhat chain automining

[Pabl0cks]

Trying to reproduce #242 in the current live challenge, I've realized the "Rigged Roll" was much smoother there, because in the extension challenge I had to refresh the blocks by hitting a regular roll or by using the faucet, in order to get a new block to be able to rig roll.

In our live version of the challenge, hardhat is configured to have block auto mining, but in our extensions it's not.

If the behaviour is too specific to implement it in create-eth maybe we should just hint it in the new readme?

hardhat: {
      mining: {
        auto: true,
        interval: 1000,
      },
      forking: {
        url: `https://eth-mainnet.alchemyapi.io/v2/${providerApiKey}`,
        enabled: process.env.MAINNET_FORKING_ENABLED === "true",
      },
    },

[rin-st]

Good catch!

Yes, we can add it in Readme. But maybe it's better to add possibility to configure hardhat network for mining? Because with mining

• hardhat becomes more similar to real networks
• sometimes I meet inconveniences/errors because of absence of mining

Any cons of mining?

[damianmarti]

Great catch!!

Yes, maybe we can an autoMining flag to the hardhat config template at create-eth (and maybe an interval too) to add this to the resulting hardhat.config.ts file. cc/ @carletex @technophile-04

If you think this is the way to go, I can add this.

[carletex]

Any cons of mining?

I guess the "issue" is that with automining you get the TX mined instantly, but when is disabled (so interval mining is enabled) you have to wait a bit (the interval time). If the interval time is 1s I guess is fine...

In any case, since we discussed, we should rethink some of the customization options for create-eth templates (allow total customization for config objects files). I'll create an issue for it so we can discuss.