[Ethereum] “Nonce too low” using contract.methods.theFunction().send()

infuraweb3js

Using web3 to build a contract from the ABI:

contract = new web3.eth.Contract(JSON.parse(abi), '0x17c91A5a6f5e3E4BEaFC478D18C4A44D88833277', { from: '0x0Ad2b5CCe78D677fD000698a7E4Cde866DE189C6', gas: 100000})

contract.methods.myFunction('constructorVariable1', 'constructorVariable2').send()

First send completes successfully. Second+ send returns the error: nonce too low

Truffle v5.1.13 (core: 5.1.13)
Web3.js v1.2.1
Ropsten testnet
Infura as HDWalletProvider node

I can't find any documentation on manually increasing the nonce using the send() method. I would have also thought nonces would be increased automatically?

I should add that there were no pending transactions during these sends.

Update:

Disconnecting and reconnecting from truffle console resolved the issue.

Best Answer

I ran to the same nonce too low message. My issue was due to adding a wallet with a private key without the 0x prefix - simply adding the 0x prefix worked. Here is my working code:

let account = web3.eth.accounts.wallet.add("0x8f88c79e3.......");

TestContract.methods.testFunction().send({
    from: account.address,
    gas: '1000000',
    value: 0,
});

Related Solutions

truffle, infura, nonce, error – How to Fix Nonce Too Low Error on Truffle + Infura Mainnet

If you're using Truffle with Infura directly (which it sounds like you are, although it's unclear why you mention MetaMask), you need to be aware that Infura is running on a server farm. If you submit a transaction, the node that receives it first may not be the same node that handles the next transaction, or that handles the eth_getTransactionCount call that gets the nonce for the next transaction.

On Ropsten, transactions will propagate quickly, and will quickly be mined, but this isn't always true on mainnet, so you need some kind of client-side nonce management.

MetaMask handles this using some special nonce-tracking middleware. It's rather disappointing that Truffle's HDWalletProvider doesn't use this middleware, since HDWalletProvider already re-uses several pieces of MetaMask middleware, and I'm half tempted to raise a pull request to include it.

In any case, here's a truffle.js that implements this via a slightly hacky workaround:

var HDWalletProvider = require("truffle-hdwallet-provider")
var NonceTrackerSubprovider = require("web3-provider-engine/subproviders/nonce-tracker")

module.exports = {
  networks: {
    mainnet: {
      network_id: "1",
      provider: function () {
        var wallet = new HDWalletProvider('candy maple cake sugar pudding cream honey rich smooth crumble sweet treat', 'https://mainnet.infura.io')
        var nonceTracker = new NonceTrackerSubprovider()
        wallet.engine._providers.unshift(nonceTracker)
        nonceTracker.setEngine(wallet.engine)
        return wallet
      }
    }
  }
}

[Ethereum] getting error nonce too low , but nonce is proper stuck since one day

This line:

var count = Web3.eth.getTransactionCount(defaultAccount,'pending');

You're starting your count at the number of outstanding/pending transactions the node is aware of. That's the wrong queue.

You could start here:

var count = Web3.eth.getTransactionCount(defaultAccount);

This will drop the next transaction on the nonce that follows the last known confirmed transaction.

It's not a good pattern, generally, to rely on the node's transaction count to set the nonce. Ideally, the software client will be aware of every transaction sent from the account and will know the correct number without asking.

Have a look over here for more info: Why does sendSignedTransaction return a tx hash BUT does not post to the Rinkeby network (React, Metamask, web3, infura)

And here: Concurrency patterns for account nonce

Hope it helps.

Best Answer

Related Solutions

truffle, infura, nonce, error – How to Fix Nonce Too Low Error on Truffle + Infura Mainnet

[Ethereum] getting error nonce too low , but nonce is proper stuck since one day

Related Topic