RPC resiliency, nonce burning, more metrics #65
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On Unichain, we see:
replacement transaction underpriced(aka nonce re-use)Note, this is not occurring on Base despite using the same logic.
The hypothesis as to why this is happening:
On Unichain, RPC providers experience extreme latency (100-1k blocks of delay). This causes the thread to get stuck waiting for confirmations which never arrive. This prevents the keys from being unlocked. When re-deploying the service, the keys are all unlocked again however the old txs are stuck in the mem-pool. Because the old txs are still stuck in the mempool, the new txs cannot be processed without first burning the nonce.
This PR adds a 10 second timeout to the awaiting confirmation process and a nonce burning method in case the tx submission fails due to
replacement transaction underpriced.Bonus: the PR also adds some new order metrics and logs.