This repository was archived by the owner on Dec 3, 2024. It is now read-only.
Nonce incremented when retrying a transaction due to gas price policy #42
Labels
bug
Something isn't working
Describe the bug
When retry policy is triggerred then new transaction is broadcasted with incremented nonce.
Configuration
It happens in Helm, prod-like configuration as well as Orchestrate suite running locally with docker-compose. Also nonce manager redis/in-memory does not take an effect. Same as setting tx idempotency key
1 Short retry policy & low tx priority
Chain configuration:
Gas price policy
2 Long chain listener backoff value & high tx priority
Chain configuration:
Gas price policy
-->
Steps to reproduce
setGreeter(string memory newGreeting)
Actual result
For both configurations, result is same. Namely tx-sender retries signing and sending transactions with incremented nonce.
This results in mining more than one transaction. Tx-Sender stops retrying after tx with lowest nonce gets finally mined.
Expected result
Retry policy should resend very same transaction with very same nonce with higher priority / gas price.
It would result in
Additional context
Machine Setup
Logs
Tx-Sender log:
Screenshots
Etherscan

Jobs. Actually, all of jobs were mined.
The text was updated successfully, but these errors were encountered: