Inconsistency in Transaction Status Reporting for Proposer and Subsequent Proving Failures

[isekaitaiku]

Describe the bug

It seems that there are instances where the proposer believes that the proposeTx has failed (as the log does not display "Propose transactions succeeded"), but in reality, the proposerTx has actually succeeded.

(This is just a guess) This appears to lead to a corresponding failure in the proving process.

I noticed it after the log disappeared, so there is no log.
I will add the log when I get it.

Steps to reproduce

1. Run both the prover and the proposer on the same server using the same private key.
2. Monitor the success logs of the proposer by running sudo docker compose --profile proposer | grep "Propose transactions succeeded".
3. Monitor the proposer address on the explorer and wait until the proposerTx is confirmed as successful.
4. Identify and observe any instances where step 3 is met but step 2 is not.

Spam policy

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

[isekaitaiku]

The Holesky node in use is located on a separate server, and no delays in the sync distance were observed when viewed through Grafana.

[trader2021]

good idea

[bungebun]

agree this

[farukana]

good improvement