A bridge transaction replacement resubmits a pending transaction from the same account with the same nonce and higher fees. It works only while the original is still unconfirmed; once it is mined, the bridge deposit has already started, and another deposit can duplicate the transfer.
A speed-up reuses the pending transaction’s nonce
On Ethereum, each account’s transactions use sequential nonces. A replacement with the same nonce competes with the original, so at most one can be included on-chain. Keep the destination, bridge call data and token amount identical when speeding up; changing them can turn a fee adjustment into a different transaction.
The Ethereum JSON-RPC method for checking an account’s transaction count with the pending tag shows one node’s view of pending activity. For context on the transfer itself, how Mantle Bridge deposits and gas work explains the source-chain step. A bridge deposit begins on that source chain, so check its explorer entry before retrying.
Check the source transaction before raising its fee
First, find the transaction hash in your wallet or the source-chain explorer. Confirm its status is pending and note its nonce, destination, amount and fee fields. For an EIP-1559 transaction, raise both maxFeePerGas and maxPriorityFeePerGas enough to clear the node’s replacement policy; there is no universal bump percentage. The EIP-1559 specification defines those fee fields, while node policy determines the required bump.
For a Mantle Bridge deposit, a pending Ethereum transaction may be sped up with the same deposit call and nonce. By contrast, if the deposit is already confirmed, the delay may be in confirmation, relay or destination processing; a fee bump cannot accelerate that transaction. Wait for its status to update before deciding whether further action is needed.
Replacing a still-pending transaction does not mean paying gas for both versions: only the version included on-chain consumes gas. If the original confirms first, the replacement cannot also execute with that nonce. Avoid submitting a fresh deposit with a new nonce while the original’s outcome is unclear, because both deposits could then confirm.
What if the wallet says the transaction is dropped?
Check the source-chain explorer and your account’s pending transaction count before acting. A transaction missing from one node’s mempool may still be known to another node, or it may have been included. If it is genuinely absent and the nonce remains unused, you can submit the intended deposit; if the nonce has advanced, identify the transaction that used it first.
Should I cancel instead of speeding up?
Cancel only if you want to abandon the deposit. A cancellation usually sends a simple transaction from the same account with the same nonce and a higher fee, but it races the original: whichever is included first uses that nonce. If the deposit wins, it proceeds; if cancellation wins, the deposit call does not execute.
Decision rule: Speed up only a verified pending deposit by reusing its nonce and exact call; if it is confirmed, wait for bridge processing instead.
Top comments (0)