You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using tx-fuzz through kurtosis and generating a lot of transactions. When there's too many transactions sent tx-fuzz crashes displaying Replacement transaction underpriced. It seems to be the problem with setting nonce when a transaction from previous iteration is still pending. In that case NonceAt may return a nonce of a pending transaction.
I see two potential fixes here:
Track nonce locally instead of making rpc call each time a transaction is created
Recover from crashes: ignore errors thrown by node and keep fuzzing
The third, and imo the best, would be a hybrid approach: tracking nonce locally and falling back to rpc method when an exception
The text was updated successfully, but these errors were encountered:
I'm using tx-fuzz through kurtosis and generating a lot of transactions. When there's too many transactions sent tx-fuzz crashes displaying
Replacement transaction underpriced
. It seems to be the problem with setting nonce when a transaction from previous iteration is still pending. In that case NonceAt may return a nonce of a pending transaction.I see two potential fixes here:
The third, and imo the best, would be a hybrid approach: tracking nonce locally and falling back to rpc method when an exception
The text was updated successfully, but these errors were encountered: