-
Notifications
You must be signed in to change notification settings - Fork 20.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
-32000, future transaction tries to replace pending #26890
Comments
I have the same error,when send transaction with nonce- n success,send nonce- n+1 will return this error after geth client upgrade |
This issue is not always reproducible, it occurs intermittently. |
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 |
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 |
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. |
This is happening widespread. |
@swoonai Please update to the newest release v.1.11.5 |
For what it's worth +1 for Matter Labs team, still an issue |
Today, I have observed this issue as well, the root cause may or may not be the same
One solution: Switch to more hiqh quality RPC service provider |
Experiencing it as well using ZK Stack! |
Got this error using Alchemy |
Got this error using |
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?
The text was updated successfully, but these errors were encountered: