Getting "nonce too low" errors after upgrading to v1.14.0 #4543
Description
Describe the bug
Since upgrading to docker image avaplatform/avalanchego:v1.14.0, our backend throws errors like:
Caused by:
0: Failed to submit: web3 error: RPC error: Error { code: ServerError(-32000), message: "nonce too low: next nonce 10633, tx nonce 10632", data: None }
1: web3 error: RPC error: Error { code: ServerError(-32000), message: "nonce too low: next nonce 10633, tx nonce 10632", data: None })[...]
Our backend logic hasn't changed and this is only happening when querying local RPC endpoints (managed internally). When pointing to external RPC providers, the errors go away. Also, this happens when querying the RPC endpoint directly, so it's not a matter of proxies querying different backends.
To Reproduce
Upgrade avalanche-go to docker image v1.14.0.
Expected behavior
Transaction can be submitted to the blockchain with the "latest" nonce as reported by the eth_getTrancasctionCount.
Screenshots
If applicable, add screenshots to help explain your problem.
Logs
Caused by:
0: Failed to submit: web3 error: RPC error: Error { code: ServerError(-32000), message: "nonce too low: next nonce 10633, tx nonce 10632", data: None }
1: web3 error: RPC error: Error { code: ServerError(-32000), message: "nonce too low: next nonce 10633, tx nonce 10632", data: None })
Metrics
If applicable, please include any metrics gathered from your node to assist us in diagnosing the problem.
Operating System
Docker image avaplatform/avalanchego:v1.14.0
Additional context
I've noticed the PR here, not sure if this can somehow trigger this behavior. What is certain is that before the Granite hardfork, everything was working as expected.
When querying the node's web3_clientVersion it returns v0.15.4 which is different from v1.14.0 which is the confirmed docker image we're running. Is this expected?
To best protect the Avalanche community security bugs should be reported in accordance to our Security Policy