Time-dependent tests with Hardhat?

Question 1

For Ganache, there are severalsolutions.

What about Hardhat? They implemented their own local blockchain, Hardhat Network, which is different to Ganache.

Question 2

The buidlerevm page says it supports ganache'sevm_increaseTime and additionally they haveevm_setNextBlockTimestamp.

Question 3

@Ismael your comment is a legitimate answer. Feel free to post it :)

Question 4

I can't test right now, but I'll add an answer when I've more time.

Question 5

Using Hardhat Network Helpers

The easiest way to do this is to use the time helpers inHardhat Network Helpers.

Install them with:

npm install @nomicfoundation/hardhat-network-helpers

And then you can use them like this:

import { time } from "@nomicfoundation/hardhat-network-helpers";async function main() {  // advance time by one hour and mine a new block  await helpers.time.increase(3600);  // mine a new block with timestamp `newTimestamp`  await helpers.time.increaseTo(newTimestamp);  // set the timestamp of the next block but don't mine a new block  await helpers.time.setNextBlockTimestamp(newTimestamp);}main();

You can check the referencehere.

Using raw JSON-RPC calls

There are two relevant RPC methods here:evm_increaseTime andevm_setNextBlockTimestamp. In both cases, they affect the next block but don't mine one.

evm_increaseTime receives a number of seconds that will be added to the timestamp of the latest block.evm_setNextBlockTimestamp receives an absolute UNIX timestamp (again, in seconds), and so it's not affected by the current block.

Examples

evm_increaseTime

// suppose the current block has a timestamp of 01:00 PMawait network.provider.send("evm_increaseTime", [3600])await network.provider.send("evm_mine") // this one will have 02:00 PM as its timestamp

evm_setNextBlockTimestamp

await network.provider.send("evm_setNextBlockTimestamp", [1625097600])await network.provider.send("evm_mine") // this one will have 2021-07-01 12:00 AM as its timestamp, no matter what the previous block has

Keep in mind that Hardhat Network validates that the new timestamp is bigger than the previous one, so you can't sendany value.

Question 6

When using this with hardhat I got this issue: Error: Transaction reverted and Hardhat couldn't infer the reason. Please report this to help us improve Hardhat.

Question 7

Did anyone face the same issue ?

Question 8

@Franco this way also works: await network.provider.send("evm_mine", [timestampInSeconds]);

Question 9

What's the difference between usingethers.provider rather thannetwork.provider? I used both and they both seem to work.

Question 10

For low-level JSON-RPC calls like these, they are the same.network.provider is "just" an EIP-1193 provider object.ethers.provider also implements that interface, but it has more functionality. I wrote about that at length here if you're interested:hackmd.io/@fvictorio/hardhat-networks-and-providers

Question 11

Anew update to Ganache has added a time parameter to theevm_mine command. Now the best way to move time is

await ethers.provider.send("evm_mine", [newTimestampInSeconds]);

It is better because you only make 1 RPC call instead of 2 in theaccepted solution.

Note that you can't move time backwards in Hardhat.

Question 12

Thanks for your answer! But this question was about Hardhat, not Ganache.

Question 13

My answer was written for hardhat in mind, I linked to the ganache update since hardhat docs forevm_mine just saysame as ganache which lead me to believe hardhat reuses some parts of ganache-cli. I am using the solution in my tests with hardhat, and they work perfectly :)hardhat.org/hardhat-network/reference/…

Question 14

github.com/trufflesuite/ganache/pull/13/files Found the ticket from the active ganache repo

Question 15

const { expect } = require("chai");const { ethers } = require('hardhat');const sevenDays = 7 * 24 * 60 * 60;const blockNumBefore = await ethers.provider.getBlockNumber();const blockBefore = await ethers.provider.getBlock(blockNumBefore);const timestampBefore = blockBefore.timestamp;await ethers.provider.send('evm_increaseTime', [sevenDays]);await ethers.provider.send('evm_mine');const blockNumAfter = await ethers.provider.getBlockNumber();const blockAfter = await ethers.provider.getBlock(blockNumAfter);const timestampAfter = blockAfter.timestamp;expect(blockNumAfter).to.be.equal(blockNumBefore + 1);expect(timestampAfter).to.be.equal(timestampBefore + sevenDays);

Question 16

this worked for me!

Question 17

For any future wanderers:

Hardhat added a network-helpers library with convenient JS interface:

Among other things, there are functions to change network time:https://hardhat.org/hardhat-network-helpers/docs/reference#time-helpers.

Some examples copied from the reference:

// advance time by one hour and mine a new blockawait helpers.time.increase(3600);// advance time to specific timestamp and mine a new blockawait helpers.time.increaseTo(newTimestamp);// set the timestamp of the next block but don't mine a new blockawait helpers.time.setNextBlockTimestamp(newTimestamp);

Question 18

What I've been using with typescript and hardhat:

import { ethers, waffle } from 'hardhat';const time = now + 86400await ethers.provider.send('evm_setNextBlockTimestamp', [now]); await ethers.provider.send('evm_mine');

Question 19

This doesn't seem to work for me in hardhat currently, if I log out the result of the first call, I get the new time I'm trying to set to, but further assertions down the line don't seem to respect that new time. Also, I had to add an empty array after theevm_mine argument since its required.Logging out thee result of theevm_mine call is 0x0

Question 20

Is there a simple way to getnow instead of(await ethers.provider.getBlock(await ethers.provider.getBlockNumber())).timestamp?

Question 21

@Martian just use "latest" instead of fetching the last block number. But other than that change, this is about as short as it gets.

Question 22

Adding to Franco's answer, there is a plugin that abstracts some of the complexities of handling time directly.

You can look its documentation inhttps://www.npmjs.com/package/@atixlabs/hardhat-time-n-mine

Question 23

Returns404. Is it moved to some different place? @GonzaloPetraglia

Question 24

Fixed the link while thisPR is open

Question 25

This is why answers w/ no content and just links are discouraged

Franco Victorio 3,01219 silver badges29 bronze badges · Accepted Answer · 2022-11-19 10:30:25Z

Using Hardhat Network Helpers

The easiest way to do this is to use the time helpers inHardhat Network Helpers.

Install them with:

npm install @nomicfoundation/hardhat-network-helpers

And then you can use them like this:

import { time } from "@nomicfoundation/hardhat-network-helpers";async function main() {  // advance time by one hour and mine a new block  await helpers.time.increase(3600);  // mine a new block with timestamp `newTimestamp`  await helpers.time.increaseTo(newTimestamp);  // set the timestamp of the next block but don't mine a new block  await helpers.time.setNextBlockTimestamp(newTimestamp);}main();

You can check the referencehere.

Using raw JSON-RPC calls

There are two relevant RPC methods here:evm_increaseTime andevm_setNextBlockTimestamp. In both cases, they affect the next block but don't mine one.

evm_increaseTime receives a number of seconds that will be added to the timestamp of the latest block.evm_setNextBlockTimestamp receives an absolute UNIX timestamp (again, in seconds), and so it's not affected by the current block.

Examples

evm_increaseTime

// suppose the current block has a timestamp of 01:00 PMawait network.provider.send("evm_increaseTime", [3600])await network.provider.send("evm_mine") // this one will have 02:00 PM as its timestamp

evm_setNextBlockTimestamp

await network.provider.send("evm_setNextBlockTimestamp", [1625097600])await network.provider.send("evm_mine") // this one will have 2021-07-01 12:00 AM as its timestamp, no matter what the previous block has

Keep in mind that Hardhat Network validates that the new timestamp is bigger than the previous one, so you can't sendany value.

When using this with hardhat I got this issue: Error: Transaction reverted and Hardhat couldn't infer the reason. Please report this to help us improve Hardhat.
@Franco this way also works: await network.provider.send("evm_mine", [timestampInSeconds]);
What's the difference between usingethers.provider rather thannetwork.provider? I used both and they both seem to work.
For low-level JSON-RPC calls like these, they are the same.network.provider is "just" an EIP-1193 provider object.ethers.provider also implements that interface, but it has more functionality. I wrote about that at length here if you're interested:hackmd.io/@fvictorio/hardhat-networks-and-providers

Movatterモバイル変換

Stack Exchange Network

Time-dependent tests with Hardhat?

6 Answers6

Using Hardhat Network Helpers

Using raw JSON-RPC calls

Examples

evm_increaseTime

evm_setNextBlockTimestamp

Your Answer

Sign up orlog in

Post as a guest

Linked

Related

Hot Network Questions

Subscribe to RSS