Lesson 8 : Nonce too high error

[Aesthetyx]

// fund function
async function fund() {
  const ethAmount = "77"
  console.log(`Funding with ${ethAmount}...`)
  if (typeof window.ethereum !== "undefined") {
    const provider = new ethers.providers.Web3Provider(window.ethereum)
    const signer = provider.getSigner()
    const contract = new ethers.Contract(contractAddress, abi, signer)
    const transactionResponse = await contract.fund({
      value: ethers.utils.parseEther(ethAmount),
    })
  }
}

During lesson 8, at around 13:17:46, when the fund function is called from the Fund Me App via browser, I am faced with the error below after clicking confirm.

eth_sendRawTransaction

  Nonce too high. Expected nonce to be 2 but got 4. Note that transactions can't be queued when automining.

To provide some context, I trashed the terminal after sending through a few transactions as I was facing a separate error prompting that I was not sending enough ETH. After executing "yarn hardhat node" again, confirming the fund transaction via metamask results in the error above.

By importing a new test account to my metamask (using Account 1 on the hardhat localhost network instead of Account 0), I was able to successfully confirm the fund transaction with no errors. However, switching back to Account 0 results in the same error happening again.

Would anyone know what is causing the nonce to be 4 instead of 2 and how would I go about fixing the above error?

Thanks!

[zeroxvee]

Click onto your metamask account avatar -> Setting -> Advanced -> Reset Account

It happens when you restart your local hardhat node. Metamask doesn't know you've restarted it and still has the nonce of whatever it was on your previous node run.

[Aesthetyx]

Thank you for this, was not aware of this reset account function in metamask, it fixed my issue.

On a sidenote, if this was the Ethereum mainnet instead of my local hardhat node, would resetting the account's transaction history not cause issues when transacting on the mainnet? Or is there some feature somewhere that would "sync" the nonce values?

[M1708]

@Aesthetyx You said you were getting this error
Not sending enough ETH.

How did you resolve this error. I am getting this error too.

[Aesthetyx]

Hey,

I am not sure what I did to solve the error but these were the things I did after running into that error and somehow the issue resolved itself:

1. I manually changed the port settings for live server to 8545 to match the port of my localhost URL which somehow made my live server's port change from 5501 to 8546. I do not understand much about what port is or how it works but I noticed that the port in my transaction details in metamask was showing port as 5500, which was different from the localhost URL's port (8545) so I thought maybe matching the two would resolve the issue. I then changed live server's port setting back to 0.
2. I changed my ethAmount from 77 to 0.1 (I doubt this is the issue, I just tested a fund transaction with the ethAmount set to 77 and the script works)
3. I used Account 1 instead of Account 0 from localhost node (also does not seem to be what was causing the issue since account 0 now works on my end without making any changes to the script)
4. I started up the node before clicking on the "go live" button
5. I also restarted my computer during the process

Not sure how I managed to resolve it but if it matters, all the actions I performed are mentioned above and the only change I made to the scripts was to change the ethAmount from 77 to 0.1.

[PatrickAlphaC]

Great work all :)

[prakhar9015]

hey guys, i think i got the SOLUTION ... here the issue is in the fund() function . , where we're passing the ethAmount value as a string to the value parameter, but we are not converting it to the expected format.

To fix this use the parseEther() function from the ethers.utils library to convert the ethAmount string to the expected format

look at my code here 👇

async function fund() {
    const ethAmount = "0.1"
    console.log(`Funding with ${ethAmount}`)

    if (typeof window.ethereum !== "undefined") {
        const provider = new ethers.providers.Web3Provider(window.ethereum)
        const signer = provider.getSigner()
        console.log(signer)

        const contract = new ethers.Contract(contractAddress, abi, signer)
        try {
            const transactionResponse = await contract.fund({
                value: ethers.utils.parseEther(ethAmount),   //  <--    👈 fix here
            })
        } catch (error) {
            console.log(error)
        }
    }
}

I hope this will fix the bug. share this if it helped you 😊

[Rami-Majdoub]

This error happens when you use Metamask with a local blockchain such as Hardhat node.
When you close (Ctrl + C) Hardhat node, all the transactions will be deleted but Metamask will keep the value of nonce.
To avoid this error, you should save the state of the blockchain (including all Txs) and load them at the startup of the node.
Unfortunately, Hardhat node does not provide a method to do this.
You can use ganache UI or CLI as a local blockchain.
Use these flags if you choose the CLI:

--database.dbPath              Specify a path to a directory to save the chain database.
-m, --wallet.mnemonic          Use a specific HD wallet mnemonic to generate initial addresses.

So instead of npx hardhat node you would run ganache -m "MNEMONIC" --database.dbPath /PATH/TO/REPO/