Bug : [Mainnet] Prover aborted tx send due to critical error: failed to get tx into the mempool

[quangtuyen88]

Describe the bug

I'm getting this err :

taiko_client_prover_relayer-1  | ERROR[06-18|02:53:14.580] Submit proof error                       blockID=76054 minTier=200 error="aborted tx send due to critical error: failed to get tx into the mempool"
taiko_client_prover_relayer-1  | ERROR[06-18|02:56:38.646] Submit proof error                       blockID=76054 minTier=200 error="aborted tx send due to critical error: failed to get tx into the mempool"
taiko_client_prover_relayer-1  | ERROR[06-18|03:00:02.711] Submit proof error                       blockID=76054 minTier=200 error="aborted tx send due to critical error: failed to get tx into the mempool"
taiko_client_prover_relayer-1  | ERROR[06-18|03:03:26.777] Submit proof error                       blockID=76054 minTier=200 error="aborted tx send due to critical error: failed to get tx into the mempool"
taiko_client_prover_relayer-1  | ERROR[06-18|03:06:50.842] Submit proof error                       blockID=76054 minTier=200 error="aborted tx send due to critical error: failed to get tx into the mempool"

Log is fine yesterday.

Raiko log is good also

Steps to reproduce

Steps to reproduce here.

Spam policy

• [X] I verify that this issue is NOT SPAM and understand SPAM issues will be closed and reported to GitHub, resulting in ACCOUNT TERMINATION.

[quangtuyen88]

I can see it's retrying each 3 or 4m . But still fail and it will run out of windows time for submit proof..

If you do retry failed need to reverted that prover transaction. I can't accept lose 250 Taiko again because weird err on mainnet. that's not acceptable.

[quangtuyen88]

The issue was solved after adding more ETH in prover balance..

1. We can't monitor our prover 24/24 because that weird err with gas bump.
2. Team need do action after some retry because 1h windows time for submitting proof.
3. We need better log clarify on issue so we can have better action. I can't even understand why I'm getting that err.

[YoGhurt111]

The recommended way is to add a prover balance alert. And will optimize the logger.