TX doesn't have the correct nonce - Metamask

Question

I'm trying to call the leafPicked() function in my contract from web3 which launches Metamask as intended. After pressing accept the transaction shows as failed along with the error message pictured below.

What am I doing wrong?

Contract Function:

function leafPicked(uint numPicked) public returns (uint, uint){
    require(numPicked < remaining_leaves);
    uint number_before_picking = remaining_leaves;
    remaining_leaves -= numPicked;
    leafWasPicked(remaining_leaves, numPicked);
    return (remaining_leaves, number_before_picking);
}

Web3 function:

  web3.eth.getAccounts(function(error, accounts) {
    if (error) {
    console.log(error);
    }

    var account = accounts[0];
    console.log(account);

    App.contracts.Plant.deployed().then(function(instance) {
      plantInstance = instance;

      // This function is not executing as intended
      return plantInstance.leafPicked(parseInt(leafNum), {from: account});

    }).then(function(result) {
      console("Result from leaf picking: ", result);
      return App.SetContractValues();
    }).catch(function(err) {
      console.log(err.message);
    });
  });

Answer 1

I had the same issue with ganache, obviously re-installing metamask is not trivial, thank goodness changing the networkId of ganache put a stop to the nonce issue in metamask.

I believe you can also "reset" your account in metamask. This will set your nonce back to Zero. You can find this option under settings.

Answer 2

There are two common problems people have when using MetaMask on private networks.

If you're running a private network, you have to be sure to set your chainId to the same as your networkId. This is for EIP 155 compatibility.

If you're running a test blockchain that you've shut down and restarted from a blank state with MetaMask connected to it, you can get MetaMask confused, because it caches some information about the network it is currently connected to, including completed transactions, which it uses to derive the correct nonce. You can clear this cache by selecting a different network in MetaMask, and then your local server again.

Answer 3

There is a new feature in Metamask for this:

https://consensys.zendesk.com/hc/en-us/articles/360004177531-Resetting-an-Account-New-UI-

Answer 4

It seems this is an ongoing Metamask issue when testing on the private networks.

It is described here: Nonce calculation is broken for private networks

And here: Truffle develop static network id interferes with MetaMask

The current solution is to reinstall Metamask - it worked for me.

Answer 5

Starting from MetaMask v3.14.1 you can reset your account as follow:

Resetting an Account In the Settings menu, MetaMask has a "Reset Account" button. This button wipes the current account's transaction history, which is used to calculate the current account nonce.

Normal users should never have a reason to use this feature.

This is useful for developers who reset a test network but want to continue using the same account, forcing MetaMask to believe this network ID is a clean network in a fresh state.

Ref: http://metamask.helpscoutdocs.com/article/36-resetting-an-account

Copied from https://stackoverflow.com/a/47429502/8303489

Answer 6

I answered this in a stackoverflow post, however, since this post comes up on top in google search, so here we go

Check your truffle.js or truffle-config.js

if you are using the HDWalletProvider like below, it seems that this is what causing the error

var HDWalletProvider = require("truffle-hdwallet-provider");
var mnemonic = "your mnemonic";

module.exports = {
  networks: {
    development: {
      provider: function() {
        return new HDWalletProvider(mnemonic, "http://127.0.0.1:8545/", 0, 50);
      },
      network_id: '*',
      gas: 9999999
    }
  },
  compilers: {
    solc: {
      version: "^0.4.25"
    }
  }
};

remove the HDWalletProvider like below, it solves mine

module.exports = {
  networks: {
    development: {
      host: "127.0.0.1",     // Localhost
      port: 8545,            // Standard Ganache UI port
      network_id: "*", 
      gas: 4600000
    }
  },
  compilers: {
    solc: {
      version: "0.5.2"
    }
  }
};

Answer 7

Genash uses the same networkId as ropsten network, and for costum url's metamask uses the same network params as the last network, so change your network to ropsten¹ and back to localhost.

Thanks CodingYourLife for the solution.

---

¹ or whatever network your local client is running on.

Answer 8

I really don't know why or how, but nothing here worked for me.. I opened the console and saw a warning ethereum.enable() is deprecated, please use eth_requestAccounts

So I just copied the code from the docs and now it works like a charm. Here's the link to the docs: https://docs.metamask.io/guide/rpc-api.html#eth-requestaccounts

And here is the link to the example: https://docs.metamask.io/guide/rpc-api.html#example

This is how I implemented the code:

if ( window.ethereum ) {
    const web3 = new Web3( window.ethereum );

    try {
        // Request account access if needed
        let handleAccountsChanged;
        await window.ethereum
            .request( {
                method: 'eth_requestAccounts'
            } )
            .then( handleAccountsChanged )
            .catch( ( error ) => {
                if ( error.code === 4001 ) {
                    // EIP-1193 userRejectedRequest error
                    console.log( 'Please connect to MetaMask.' );
                } else {
                    console.error( error );
                }
            } );
    } catch ( error ) {
        // handle error
    }
}

Answer 9

I would like to add one more solution as none of these had worked for me.

I clicked on the Metamask chrome extension then went to My Accounts > Settings > Advanced > Reset Account. This resets the accounts transaction history but won't change the balances or require you to re-enter your seed phrase.

Answer 10

In the MetaMask setting > go to advanced setting > turn on custom nonce.

After turning on Custom nonce, you can add your custom nonce before making any transaction.

The custom nonce should be the account nonce. Here in this case it is 4. (you can get the account nonce in the error)

If this works for anyone please let me know.

Answer 11

You should reset your metamask account by going to setting option and reset account. Please check the metamask docs.

Answer 12

I had the same problem solved by:

1. As advised by Phillip Gibb in the above, I changed the Ganache network id to 5778. Ganache will restart.

2. Re-connect MetaMask to Ganache.

   check your account. If only Account 1, this is a good sign. You can manually import other accounts. But if more than one account still exist, that's not a good sign. You may have to change to other Ganache network id and reconnect MetaMask.

3. Migrate contract

truffle migrate --reset --network development

4. Contract deployed. Test new transactions ok.

Answer 13

I faced the same issue but I am using ethers version 6 (6.2.3) and Ganache To solve this I am waiting for confirmation blocks as below

//Deploying contract
 const contract = await contractFactory.deploy();
 const deployTxn = await contract.deploymentTransaction().wait(2); //this is the solution you can change wait to 1 block also it will work 

// Calling contract functions  
 const transactionResponse = await contract.store('7');
 const transactionReceipt = await transactionResponse.wait(1); // You can remove this line if you don't want to wait post txn

Complete code for deployment and calling functions

const { ethers, JsonRpcProvider } = require('ethers');
const fs = require('fs-extra');
async function main() {
  const provider = new JsonRpcProvider('http://127.0.0.1:7545');

  const wallet = new ethers.Wallet(
    'private key here',
    provider
  );

  const abi = fs.readFileSync('./SimpleStorage_sol_SimpleStorage.abi', 'utf8');
  const binary = fs.readFileSync(
    './SimpleStorage_sol_SimpleStorage.bin',
    'utf8'
  );
  const contractFactory = new ethers.ContractFactory(abi, binary, wallet);
  console.log('Deploying, Please wait...');
  const contract = await contractFactory.deploy();
  const deployTxn = await contract.deploymentTransaction().wait(2);
  const transactionResponse = await contract.store('7');
  const transactionReceipt = await transactionResponse.wait(1);
  const favNum = await contract.retrieve();
  console.log(favNum.toString());
}

main()
  .then(() => process.exit(0))
  .catch((error) => {
    console.error(error);
    process.exit(1);
  });