feat: add miner.timestampIncrement option

[davidmurdoch]

By default ganache uses the system clock time for automatically mined blocks. This behavior is convenient, but results in nondeterminism, invalid block timestamps*, and can cause issues with relative block timestamp dependent contracts and tests. There were workarounds for all of these issues (by manually mining via evm_mine({timestamp})) but a built in solution was clearly necessary.

Ganache now permits the use of a new --miner.timestampIncrement option which can be used to set the amount of seconds between consecutive blocks, regardless of how much system time has passed. The default value, "clock", retains the previous default behavior of using the system time for each block.

The following example will start ganache instructing it to increment each new block's timestamp by 1 second from 1649736000000:

$ ganache --time 1649736000000 --miner.timestampIncrement=1

* The Ethereum Yellowpaper defines: $H_S > P(H)_{H_S}$ where $H_S$ is the timestamp of Block $H$ and $P(H)$ is the parent block.

[jeffsmale90]

Should we open a PR on https://github.com/mds1/convex-shutdown-simulation to use this new configuration?

[davidmurdoch]

Should we open a PR on https://github.com/mds1/convex-shutdown-simulation to use this new configuration?

We will update it, yes.