Open 314159265359879 opened 1 month ago
It is possible this only occurs on an address that hasn't signed any transactions yet. I just retested on an other address that already had a transaction with nonce 0 processed and then this didn't occur.
This seems like a self inflicted wound, no? You edited the nonce to 20 - is the expectation that if you edit the nonce we then revert back to the previous nonce value before you edited it?
This issue used to be solved, not sure if there is a change to the API or the wallet. It is my understanding that the "next nonce" api should know if there is a missing nonce between the last processed transaction nonce and the lowest nonce still pending.
reproduction steps:
The API or Wallet wrongfully deduces that the next nonce is 21, while there is a gap of nonce 0 through 19 before 21 can get processed.
Tested on the public testnet.