New answers tagged

0

I got the same error using truffle console and fixed it: instance.method(param1, param2, { nonce: YOUR_ACTUAL_NONCE }) After this the nonce is back on track. Probably it works in the same way, when executing the script. By the way, simplest way to find your nonce is too check the latest transaction of the account on a blockexplorer.


0

tx2 will not succeed. The nonce3 tx must come after the nonce2 tx. It is an invalid block for the nonce3 tx to come before the nonce2 tx. No rational miners will create such a block, because no other miner will build on it. Should the order of positions match the order of nonces in each tx? For clarity, it doesn't have to match 1:1. tx3 could be in ...


0

The transactions of the same EOA will always execute in the order of the nonce. This is necessary to ensure that the account can pay the required fees before processing a tx.


1

This happens because eth_getTransactionCount returns the nonce of mined transactions but not the pending ones. So in your case, under heavy load, there will be some transactions that are still pending but not counted by calling eth_getTransactionCount. I've been looking for a solution for this problem but I haven't found an official one. However, you can ...


0

An account nonce starts at 0. The nonce goes up by 1 if the transaction is an outgoing transaction, whatsoever the transaction succeeds or fails. Incoming transaction do not change the nonce of the receiver.


Top 50 recent answers are included