#Hardhat errors

The most common source of errors is trying to import the Hardhat Runtime Environment from your config or a file imported from it. This is not possible, as Hardhat can't be initialized while its config is being defined.

You may also have accidentally imported hardhat instead of hardhat/config.

Please make sure your config file is correct.

To learn more about how to access the Hardhat Runtime Environment from different contexts go to https://hardhat.org/hre

#HH10: Attempted to modify the user's config

An attempt to modify the user's config was made.

This is probably a bug in one of your plugins.

Please report it to help us improve Hardhat.

#HH11: Invariant violation

An internal invariant was violated. This is probably caused by a programming error in hardhat or in one of the used plugins.

Please report it to help us improve Hardhat.

#HH12: Hardhat is not installed or installed globally

You tried to run Hardhat from a global installation or not installing it at all. This is not supported.

Please install Hardhat locally using npm or Yarn, and try again.

#HH13: ts-node not installed

You are running a Hardhat project that uses typescript, but you haven't installed ts-node.

Please run this and try again: npm install --save-dev ts-node

#HH14: typescript not installed

You are running a Hardhat project that uses typescript, but it's not installed.

Please run this and try again: npm install --save-dev typescript

#HH15: You are not inside a Hardhat project and Hardhat failed to initialize a new one

You are trying to run Hardhat outside of a Hardhat project, and we couldn't initialize one.

If you were trying to create a new project, please try again using Windows Subsystem for Linux (WSL) or PowerShell.

You can learn how to use Hardhat by reading the Getting Started guide.

#HH16: conflicting files during project creation

You are trying to create a new hardhat project, but there are existing files that would be overwritten by the creation process.

Either try using a new directory name, or remove the conflicting files.

#HH17: Invalid big number

Hardhat attempted to convert the input value to a BigInt, but no known conversion method was applicable to the given value.

#HH18: Corrupted lockfile

Some versions of NPM are affected by a bug that leads to corrupt lockfiles being generated.

This bug can only affect you if you, or someone at your team, installed the project without a lockfile, but with an existing node_modules.

To avoid it, please delete both your node_modules and package-lock.json, and reinstall your project.

Note that you don't need to do this every time you install a new dependency, but please make sure to delete your node_modules every time you delete your package-lock.json.

#HH19: Hardhat config with .js or .ts extension in an ESM project

Your project is an ESM project but your Hardhat config uses an .js or .ts extension. Hardhat config files cannot be an ES module. To fix this, rename your Hardhat config to use the .cjs extension.

#HH20: Initializing a TypeScript sample project in an ESM project

Your project is an ESM project (you have "type": "module" set in your package.json) and you are trying to initialize a TypeScript project. This is not supported yet.

#HH100: Selected network doesn't exist

You are trying to run Hardhat with a nonexistent network.

Read the documentation to learn how to define custom networks.

#HH101: Connected to the wrong network

Your config specifies a chain id for the network you are trying to use, but Hardhat detected a different chain id.

Please make sure you are setting your config correctly.

#HH102: Missing `data` param when calling eth_sign.

You called eth_sign with incorrect parameters.

Please check that you are sending a data parameter.

#HH103: Unrecognized account

You are trying to send a transaction or sign some data with an account not managed by your Ethereum node nor Hardhat.

Please double check your accounts and the from parameter in your RPC calls.

#HH104: Missing transaction parameter

You are trying to send a transaction with a locally managed account, and some parameters are missing.

Please double check your transactions' parameters.

#HH105: No remote accounts available

No local account was set and there are accounts in the remote node.

Please make sure that your Ethereum node has unlocked accounts.

#HH106: Invalid HD path

An invalid HD/BIP32 derivation path was provided in your config.

Read the documentation to learn how to define HD accounts correctly.

#HH107: Invalid JSON-RPC value

One of your transactions sent or received an invalid JSON-RPC QUANTITY value.

Please double check your calls' parameters and keep your Ethereum node up to date.

#HH108: Cannot connect to the network

Cannot connect to the network.

Please make sure your node is running, and check your internet connection and networks config.

#HH109: Network timeout

One of your JSON-RPC requests timed out.

Please make sure your node is running, and check your internet connection and networks config.

#HH110: Invalid JSON-RPC response

One of your JSON-RPC requests received an invalid response.

Please make sure your node is running, and check your internet connection and networks config.

#HH111: Could not derive an HD key

One of your HD keys could not be derived.

Try using another mnemonic or deriving less keys.

#HH112: Invalid JSON-RPC value

One of your calls sent or received an invalid JSON-RPC DATA value.

Please double check your calls' parameters and keep your Ethereum node up to date.

#HH113: Invalid `data` param when calling eth_signTypedData_v4.

You called eth_signTypedData_v4 with incorrect parameters. Please check that you are sending a data parameter with a JSON string or object conforming to EIP712 TypedData schema.

#HH114: Incompatible fee price parameters

You are trying to send a transaction with a locally managed account, and its parameters are incompatible. You sent both gasPrice, and maxFeePerGas or maxPriorityFeePerGas.

Please double check your transactions' parameters.

#HH115: Missing fee price parameters

You are trying to send a transaction with a locally managed account, and no fee price parameters were provided. You need to send gasPrice, or maxFeePerGas and maxPriorityFeePerGas.

Please double check your transactions' parameters.

#HH116: Missing `address` param when calling personal_sign.

You called personal_sign with incorrect parameters.

Please check that you are sending an address parameter.

# Task definition errors

#HH200: Could not add positional param

Could add a positional param to your task because there is already a variadic positional param and it has to be the last positional one.