hardhat

This version updates the Chiado network configuration to use the up to date URLs.

This version adds support for using the Hardhat network helpers on the Anvil network (thanks @tmigone!)

This release adds experimental support for ESM in typescript projects.

In addition to that, the hardhat-shorthand tool (hh) now supports scoped tasks.

This release fixes a couple of issues:

• A problem in low-traffic chains that resulted in txs using a maxPriorityFeePerGas of 0, which were then rejected by the node.
• A bug in the compiler downloader that was triggered in big projects that used many different versions of solc.

Besides that, the project initialization now uses the latest version of the Hardhat Toolboxes.

@nomicfoundation/hardhat-web3-v4 is a new plugin that lets you use the latest version of the Web3.js library, developed as a collaboration between the Nomic Foundation and ChainSafe.

This release adds support for the polygonZkEVM and polygonZkEVMTestnet networks. It also fixes a minor issue related to a case-sensitive address comparison for detecting verified contracts.

This version of the viem-based Hardhat Toolbox bumps the version of hardhat-verify. This is a new major because the new version of that peer dependency is not compatible with the previous one, but you can consider this a low-risk upgrade.

This version of Hardhat Toolbox bumps the versions of hardhat-verify and typechain. This is a new major because the new versions of those peer dependencies are not compatible with the previous ones, but you can consider this a low-risk upgrade.

This release adds support for passing block tags as bigints.

This new version of Hardhat introduces a new feature: Configuration Variables!

Configuration variables let you use values in a configuration file without making them part of your project. They work as a replacement for environment variables and dotenv, but are more flexible and powerful. Read our guide to learn more.

This version also adds support for solc v0.8.22.

This release fixes a problem with the Vyper compiler downloader.

This new major version of hardhat-verify adds support for Sourcify. Sourcify verification is disabled by default, but you can enable it by adding this entry to your config:

module.exports = {
  // ...
  sourcify: {
    enabled: true,
  },
};

Check our docs to learn more.

This release adds ignition deploy to our telemetry-reported tasks.

This releases fixes a problem with Hardhat's compiler download caused by a fix in the latest version of undici.

This new version of Hardhat includes a new option when initializing a project: you can now start a project that uses Viem instead of ethers. To learn more about this, check our announcement.

This version also makes a small change to the logs shown during compilation: now the targeted EVM version (or versions) is shown.

This is the first release of our new hardhat-viem plugin. To learn more about it, check our announcement.

This is the first release of our new Viem-based Toolbox. To learn more about it, check our announcement.

This version of Hardhat adds support for scoped tasks.

You can now create scopes to group multiple tasks that are related in some way:

const myScope = scope("my-scope", "Scope description");

myScope.task("my-task", "Do something")
  .setAction(async () => { ... });

myScope.task("my-other-task", "Do something else")
  .setAction(async () => { ... });

Thanks to @zemse, who kickstarted the work on this!

This version of Hardhat adds support for the debug_traceCall method.

Besides that, Hardhat projects are now initialized with npx hardhat init instead of npx hardhat. The latter command still works but it will produce a warning. See https://github.com/NomicFoundation/hardhat/issues/2594 for the rationale behind this change.

This version of Hardhat changes the default evmVersion to paris for solc versions newer than or equal to 0.8.20.

Starting from version 0.8.20, solc changed the default target EVM version to Shanghai. Among other things, this meant that the generated bytecode could (and most likely would) contain the new PUSH0 opcode.

Up until this point, Hardhat always delegated to solc the decision of which EVM version to target. But there are two things that are different today: many users develop for non-mainnet chains, and not every chain has adopted the Shanghai hardfork yet. This means it's possible that you develop a contract which works locally (Hardhat's default hardfork is still Shanghai, because we follow the current mainnet hardfork) but that then doesn't work after deploying it.

If you are sure you are going to deploy in a network that supports the Shanghai hardfork, you can change the target EVM like this:

module.exports = {
  solidity: {
    version: "0.8.20",
    settings: {
      evmVersion: "shanghai",
    },
  },
};