[Application Development] Replacement Transaction Underpriced Error on OP Mainnet After Deployment Timeout

[AdamDawidKrol]

Did you check the documentation?

• Yes
• No

Documentation Feedback (Optional)

No response

What type of issue are you experiencing?

• Error
• Feature Request
• General Question

Issue Description

I attempted to deploy a contract on OP Mainnet from address 0xCbeB59d63214d90575055435eAe5435C35AFfad2, using both QuickNode and the public RPC (https://mainnet.optimism.io). The workflow was:

1. Sent the deployment transaction.
2. Waited several minutes—no confirmation (timeout).
3. Resubmitted the same transaction. Immediately received: replacement transaction underpriced
4. Increased maxFeePerGas and maxPriorityFeePerGas repeatedly, but the error persisted.
5. Incremented the nonce and retried; again the transaction timed out, and any replacement attempt always returned the same "underpriced" error.
6. After these attempts, even a simple ETH transfer via MetaMask failed outright (see screenshot).

I experienced the same issue when using both viem and Forge alone (without viem). The same problems happened when I did this operations from the address 0x2D611BE1e2E49C7b639A88b507b532DaE35e492b.

Steps to Reproduce

To be added soon.

Are you using a specific library or SDK?

• OP-SDK
• Viem
• Other
• Not Sure

Are you using the latest version of the library/SDK?

• Yes
• No

Environment Details

No response

Troubleshooting Attempts

No response

What type of support do you need?

• Technical support for issue resolution
• Feature implementation guidance
• General advice or consultation
• Documentation or learning resources

Additional Information

View on block explorer and Copy transaction ID are dead links, cannot be clicked.

Feedback

No response

[opfocus]

Please check if your transaction has been successful, if successful, please provide the transaction hash

[AdamDawidKrol]

All the transactions that were pending from yesterday were included in the block at the same time, so the problem disappeared . One of the transactions I sent yesterday, that was included today: 0x27be3e4a915d037803b94a767dcff5290639d7e093be4ec8ce1363cd850b6959. I wonder what this issue may be caused by (long waiting time for some of the transactions, almost a day).

[imtipi]

possible mempool issue,next time please use other address and try again

[AdamDawidKrol]

This is what i thought. As far as I know mempool on optimism is private, so I couldn't confirm that. The once specific contract on our side was problematic and was causing the same behavior (being stuck in the mempool) for all the addresses we tried.

[imtipi]

the previous mempool issues we know only limited to single address,if you can't execute that tx on other address,it might be other problem