What changed (plus any additional context for devs)
I was testing #5869 and realized that when sending a transaction that gets rejected by the flashbots API (ex. gas=0) we still continue monitoring it as if it was received ok and we wait forever, messing up nonces.
This PR considers tx status UKNOWN by the flashbots api as failed, which means the node never received the transaction.
Fixes RNBW-4748
What changed (plus any additional context for devs)
I was testing #5869 and realized that when sending a transaction that gets rejected by the flashbots API (ex. gas=0) we still continue monitoring it as if it was received ok and we wait forever, messing up nonces.
This PR considers tx status UKNOWN by the flashbots api as failed, which means the node never received the transaction.
Screen recordings / screenshots
I've tested the whole flow and executed a swap https://etherscan.io/tx/0x6979ab9040f846e5d6b7df09c0fe7dd8314ca7ee05a247485c9935b0c3fa752b without any problems which is why I'm closing RNBW-4748
What to test