MetaMask not picking up Hardhat accounts on port 8545 in Firefox

As a developer using Web3 and Solidity-based contracts, you are probably used to working with MetaMask. However, when connecting to local development environments like Hardhat, you may encounter issues that prevent the wallet from retrieving accounts correctly. Today, we will explore one such issue: MetaMask not picking up hardhat accounts on port 8545 in Firefox.

Problem

When you connect your Hardhat node to the test network (localhost:8545) using the MetaMask Localhost Test Network option, it seems like the wallet should automatically pick up the correct account from the list. However, this is not always the case. In some cases, the first account selected is completely different from the actual accounts you specified.

Solution

To resolve this issue, we will investigate the possible causes and provide a step-by-step solution to resolve the issue.

Cause 1: Incorrect account selection

One potential cause of this issue is that MetaMask’s Localhost Test Network configuration does not match the IP address of your hardhat node ( If the wallet selects the wrong account, it will not select the correct one from the list.

To verify this:

• Open MetaMask in Firefox and go to
  Network >
  Advanced Settings.

• Make sure “Auto Select Account” is enabled and set to match the IP address of your hardhat node (

Cause 2: Incorrect wallet configuration

Another potential cause of this issue is incorrect wallet configuration on your Hardhat node.

To resolve:

• Make sure you have a newer version of the MetaMask extension.

• Make sure you have updated your hardhat.config.js file to include the correct IP address for your local development environment (e.g.

Troubleshooting Steps

To resolve the issue, try the following:

Step 1: Check your wallet configuration

– Make sure MetaMask is installed on your browser.

– Make sure you have updated your Hardhat node to include the correct IP address.

Step 2: Set up a Localhost test network

– Go back to your MetaMask configuration.

– Change the “Test Network” to match the IP address of your hardhat node (

– Save and restart MetaMask.

Step 3: Review your hardhat node configuration

– Check your hardhat.config.js file for any incorrect configurations that might be causing the issue.

– Make sure you are using the correct network settings and IP address (

Conclusion

If you have tried the troubleshooting steps above and are still having issues with MetaMask selecting a hardhat account on port 8545, it is likely due to incorrect wallet configuration or a mismatch between the IP address of your Hardhat node and the Localhost Test Network setting.

By following these steps, you should be able to resolve this issue and ensure that MetaMask is selecting the correct account from the list when connecting to your local development environment using Hardhat.

ethereum calculate hashes second