Skip to content
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

nonce too low: next nonce 185, tx nonce 184 #85

Open
hexdigest opened this issue Feb 22, 2024 · 0 comments
Open

nonce too low: next nonce 185, tx nonce 184 #85

hexdigest opened this issue Feb 22, 2024 · 0 comments

Comments

@hexdigest
Copy link

Hi,

I'm seeing transactions stuck forever in eth-tx-manager with the following error message:

cdk-validium-eth-tx-manager  | 2024-02-22T22:41:10.052Z	ERROR	ethtxmanager/ethtxmanager.go:416	failed to send tx 0xa530490da3ce9897aed17b0446880c0166b4654a8bc43b2c442d87daffd47d18 to network: nonce too low: next nonce 185, tx nonce 184	{"pid": 1, "version": "v0.0.3-hotfix6", "owner": "sequencer", "monitoredTxId": "sequence-from-11-to-12", "createdAt": "2024-02-22T22:40:39.207Z", "from": "0x1E30d96d79b3dA314f855880122b3F285a5bc1CC", "to": "0xB2995479B92AeFE322173fA823C1A4DbD655aDe8"}
cdk-validium-eth-tx-manager  | github.com/0xPolygonHermez/zkevm-node/ethtxmanager.(*Client).monitorTx
cdk-validium-eth-tx-manager  | 	/src/ethtxmanager/ethtxmanager.go:416
cdk-validium-eth-tx-manager  | github.com/0xPolygonHermez/zkevm-node/ethtxmanager.(*Client).monitorTxs.func1
cdk-validium-eth-tx-manager  | 	/src/ethtxmanager/ethtxmanager.go:269

I use v0.0.3-hotfix6 version (checked out the tag and built it myself) I think there are two bugs probably:

  1. Assigning invalid nonce to begin with
  2. Not updating the nonce if the assigned nonce didn't work from the first try.

I tried v0.0.3-hotfix6 version (checked out the tag and built it myself) and I also tried the recent ethtxmanager/ethtxmanager.go from the develop branch. None of them worked.

I don't think this condition ever works if nonce is incorrect from the very beginning (v0.0.3-hotfix6):

	if !confirmed && hasFailedReceipts && allHistoryTxsWereMined {

in my case all these variables are always false

Can you please advise?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant