Estimate Slippage Before Retrying a Stuck Destination Swap

If a destination swap is stuck, check whether the pool can deliver the minimum output your transaction requires before you retry it. A bridge transfer may have completed while the separate swap on the destination chain failed or remains pending, so first identify which step is unfinished.

Knowing the pool’s depth can help you tell a retryable price limit from a transaction that needs different routing.

A bridge moves or represents the asset on another chain; a destination swap then trades it against liquidity available there. That trade can have a different price from the one shown when you started, especially if the pool is shallow or the quote has aged. For background on how assets and execution fit together, see this guide to Wormhole bridge transfers and integration details.

How do I estimate slippage from pool reserves?

For a simple constant-product pool, reserves give a rough way to estimate the price impact of a trade. If the pool holds reserve amounts X and Y, and you sell an amount ΔX into it, the idealized output before fees is approximately Y × ΔX ÷ (X + ΔX). This captures the pool’s curve: as your trade grows relative to the reserve, each additional unit receives a worse price.

For example, compare your input with the pool’s reserve of the token you are selling, then compare the estimated output with the spot-price output. The gap is a rough price-impact estimate, not a promise of what the swap will return. Fees, routing through multiple pools, token transfer behavior and trades that land before yours can all change the result.

For a multi-hop route or a concentrated-liquidity pool, reserve arithmetic is only a screening tool. Liquidity may be concentrated around some prices and thin beyond them, so the route’s own quote or simulation is more useful than a single reserve snapshot. Treat any estimate as stale if the market or pool state has moved since it was obtained.

What does minimum output tell me?

The transaction’s minimum output is the lowest amount of the destination token the swap is allowed to deliver. It is commonly calculated from a quoted output and a slippage tolerance: a wider tolerance lowers the minimum, making execution more likely but allowing a worse fill. The tolerance does not improve the pool’s price; it changes the limit the transaction will accept.

Compare the current expected output with that minimum, and check the transaction status on the destination chain. If the pool’s available liquidity now implies output below the minimum, the swap can revert even though the bridge step succeeded. If the swap is still pending, submitting another transaction may create a duplicate attempt; confirm its status before trying again.

Should I retry, split the trade or change the route?

Use the estimate to compare practical options, then rely on a fresh quote or simulation before signing. A smaller trade may move the pool price less, but splitting can add transaction costs and expose each piece to changing prices. A deeper route may reduce impact while adding another pool, fee or execution step.

• Check whether the bridge transfer completed and the destination asset is available.
• Refresh the route quote and inspect its expected output and minimum output.
• Compare the trade size with the relevant pool liquidity; test a smaller amount if impact is high.
• Include destination network fees and route fees when judging whether another attempt is worthwhile.

For most readers, the better first move is to refresh the quote and check the exact failed step, not to raise slippage tolerance blindly. If the estimated output still misses the minimum, choose a smaller amount or a route with more usable liquidity; a larger tolerance only makes a poor fill easier to accept.