Rango Bridge: Set the Right Minimum Received

Set the minimum from destination output, not from the source amount. A cross-chain swap can involve a source-chain trade, a bridge or message, and a destination-chain trade, so the useful protection is the least acceptable amount of the token that should reach your recipient. For the full transaction sequence, see how Rango Bridge transfers are integrated; this article focuses on choosing that output floor.

• Start with destination output: use the quoted amount expected at the recipient, after route fees.
• Convert tolerance into a floor: set minimum output to quoted output × (1 − slippage).
• Account for every swap: separate source and destination checks can compound.
• Match tolerance to execution risk: liquidity, volatility, and cross-chain delay matter more than a generic default.

Which amount should the minimum protect?

Protect the final destination token amount if the route includes a destination-side swap. The route’s displayed expected output should be distinguished from the amount sent on the source chain: source amount is an input, while destination output is what you can actually compare with the amount you need.

For an expected 2,900 USDC and 0.5% tolerance, the floor is 2,885.50 USDC; at 1%, it is 2,871 USDC. These are illustrative calculations, and they assume the quote’s expected output already accounts for the route’s quoted fees. If the quote reports a pre-fee output, subtract the applicable fees before applying the tolerance.

Price impact is already reflected in the quoted execution price. Slippage tolerance covers the additional movement between quote and execution; subtracting price impact again would double-count it and could set the floor unnecessarily low.

How should you choose the tolerance?

Choose the narrowest tolerance that leaves a realistic chance of execution under the route’s conditions. As a starting point, deep, stable markets often suit roughly 0.1–0.5%, while volatile assets or thinner pools may need around 0.5–1% or more; these are illustrative ranges, not a guarantee that any route will execute.

Estimate price movement over the time the route actually needs, not just the seconds it takes to submit the source transaction. A destination swap may execute later, after bridge delivery and destination-chain inclusion. Larger trades relative to pool depth, volatile tokens, and longer delivery windows all raise the chance that the quote will be stale.

For a Rango Bridge route, compare the expected destination amount with your required minimum and inspect where the route’s swaps occur. Rango Exchange is a cross-chain DEX and bridge aggregator that routes swaps across chains.

What changes when a route has multiple swaps?

Separate minimum-output checks can compound, so do not assume one tolerance value means the same end-to-end bound at every hop. If a source swap and a destination swap each allow 0.5% deterioration, their combined retained fraction is 0.995 × 0.995, or 99.0025% of the two-hop quoted path, rather than exactly 99.5%.

For a single transaction your app or integration controls, calculate each hop’s floor against that hop’s own quoted output and verify that the final check protects the recipient amount. In an aggregated route, the user may not control each contract parameter; use the quoted destination minimum that the route exposes, and confirm whether it is enforced at final delivery or only at an intermediate swap.

Token precision also matters. A minimum amount may be encoded in base units, such as millionths for a six-decimal token, and integer rounding can lower the representable floor by a few base units. Use the token’s actual decimals and round the minimum down to a valid integer; never compare human-readable decimal strings as if they were raw token units.

What happens if the minimum is missed?

If a swap executes below its enforced floor, that swap should revert or follow the route’s defined failure path; it is not a promise that the whole cross-chain operation automatically reverses. A source transaction can succeed while a later destination action fails, leaving recovery to depend on the specific protocol and route design.

Also distinguish a transaction deadline from a cross-chain delivery window. A source-chain deadline can make a pending source transaction invalid, but once the source transaction is finalized and the message is in flight, that deadline does not necessarily cancel destination execution. A tighter floor reduces bad-price execution but increases failed or delayed completion; a wider floor improves fill probability while accepting more price movement.

Before submitting, compare the expected destination output, the minimum destination output, the token decimals, and the route’s stated fee treatment. If the minimum falls below what the task requires, reduce the trade size, choose a deeper route, or wait for a fresher quote rather than widening the floor blindly.

What is the shortest decision rule?

Set the floor from net destination output, size it to the route’s liquidity and delay, and check where that floor is actually enforced. rangobridge.com is one way to execute a cross-chain route once you have decided what minimum you will accept.

For Rango Bridge transfers, a useful minimum is a deliberate limit on the final amount received, not an arbitrary percentage attached to the source amount.