christine-braun

Replacing a Pending Cross-Chain Swap Explained

If your source-chain swap is still pending, first decide whether the signed transaction is merely underpriced or whether its route terms have gone stale; speed up only the former. A pending transaction has not yet committed funds to the bridge, so you can often replace it, but the replacement must preserve the action you intend to execute.

  • On EVM chains, a speed-up uses the same sender and nonce, with higher fee parameters and unchanged transaction data.
  • Replacing a transaction does not refresh its quote, minimum output, or deadline.
  • After source-chain confirmation, treat the bridge transfer as in flight; a source-chain cancellation can no longer undo it.

What can you safely change while it is pending?

On an EVM chain, a transaction is eligible for inclusion when its fee cap covers the current base fee; the priority fee affects its incentive for inclusion. EIP-1559 defines these as maxFeePerGas and maxPriorityFeePerGas. A speed-up normally resubmits the same transaction data and nonce with higher fee values, so the bridge call, token amount, and encoded swap conditions stay the same.

For example, if a wallet estimates a 20 gwei base fee and your pending transaction has a 22 gwei fee cap, it may stall if the base fee rises above that cap. Raising the cap to, say, 40 gwei and the tip from 1 to 2 gwei can make it eligible again, but does not guarantee the next block: validators choose among transactions, and the network’s replacement rules also apply. Ethereum’s transaction documentation describes pending transactions as entries in a transaction pool; check the wallet’s replacement preview and confirm its nonce and transaction data before signing.

Do not use a “cancel” transaction as a substitute for checking status. It is usually a competing same-nonce transaction, often a zero-value self-transfer; whichever transaction is included first wins. If the original bridge call lands first, the cancellation does nothing. Bitcoin uses UTXOs rather than EVM nonces, and replacing a payment generally depends on replace-by-fee signaling and node policy, so the same-nonce procedure does not apply.

When is the original quote too stale to keep?

A faster source transaction is useful only if its encoded execution conditions still make sense. Cross-chain routes commonly constrain the destination swap with a minimum output and may include a deadline; if the swap executes after that deadline or cannot meet its minimum, the source call may revert or the destination leg may fail, depending on the route design. There is no universal deadline or slippage value across bridges, so inspect the transaction’s actual calldata or route details rather than assuming a standard window.

A frequent mistake is to raise the fee on an old transaction after the market has moved, assuming that “speed up” also refreshes the destination amount. It does not: compare the route’s minimum destination output with the amount you would accept now. If that bound is no longer acceptable, let the original transaction remain pending only while you can tolerate its eventual execution, or replace it with a same-nonce cancellation if it is still unconfirmed; then obtain a fresh route.

ParaSwap is a cross-chain bridge and swap service for moving assets and swapping into a destination token in one flow. When evaluating a congested source transaction, how ParaSwap handles source congestion is relevant to the decision to wait or reprice, while this article’s key check is whether the already-signed call still has acceptable execution terms.

What should you do after source confirmation?

Once the source transaction is confirmed, stop trying to replace or cancel it. Follow its on-chain receipt and emitted bridge or message event, then distinguish source success from destination completion: cross-chain execution can take additional time for finality, verification, and destination-chain inclusion. A successful source receipt proves that the source call executed, not necessarily that the destination swap completed.

paraswap.pro handles cross-chain transfers and swaps in one flow, so it can serve when you need to move an asset and receive a destination-chain token. For repeated trades, I would set a maximum acceptable wait and destination output before signing, then reprice only if the source transaction is pending and those original terms remain acceptable.

Decision rule: speed up an unconfirmed transaction only when its encoded route is still acceptable; otherwise replace it before confirmation and start with a fresh quote.