-32000, future transaction tries to replace pending

[xihucuyu888]

node error: {-32000, future transaction tries to replace pending}
I send 2 txs with nonce 0 and 1 to the geth simultaneously and the node return this error, why?

[starwill]

I have the same error，when send transaction with nonce- n success，send nonce- n+1 will return this error after geth client upgrade

[xihucuyu888]

This issue is not always reproducible, it occurs intermittently.

[MariusVanDerWijden]

This is the new rule added in 1.11.4, A future transaction can not be added to the tx pool if it would replace pending transactions. This is a safety mechanism. Is this happening with transactions that you send via eth_sendRawTransaction?

[MariusVanDerWijden]

Okay I looked through the code, seems we check this for local transactions as well. I think we can skip this check for local transactions

[karalabe]

There is a slight race if you submit multiple transactions currently. Transaction N enters the pool but will be marked as executable a bit later (hundreds of millisecs I think), in which time N+1 might be rejected. The quick and dirty solution currently it to wait a bit before subsequent nonce submissions. We'll make the above mentioned protection a bit smarter not to have this bug in the next release.

[swoonai]

This is happening widespread.

[MariusVanDerWijden]

@swoonai Please update to the newest release v.1.11.5