Start typing to search this publication.
How to Restake Stablecoins and LSTs
Open menu

Subscribe to How to Restake Stablecoins and LSTs

Get new posts delivered straight to your inbox.

Jumper bridge: How It Works From Quote to Arrival

How to Restake Stablecoins and LSTs
2 min read

Jumper bridge asks LI.FI to compare routes combining DEX swaps and bridges, then executes the route you choose through LI.FI contracts. The selected bridge delivers funds on the destination chain, so its settlement model shapes the wait and the trust assumptions. For more on what the Jumper crypto bridge does when you move assets between chains, see Jumper bridge.

How Does Jumper Build a Quote?

The Jumper cross-chain bridge uses your source chain, token, amount, destination token and slippage tolerance to request routes from LI.FI. A route can combine a source swap, a bridge transfer and a destination swap. This lets you start with one asset and request another on a different chain, even when the bridge carries an intermediate token.

Each quote estimates the output and the work needed along that path. DEX price impact, bridge costs and transaction gas can change which route looks attractive. Slippage tolerance sets the minimum output a swap may accept; it does not lock the quoted price. Compare the expected output alongside the bridge and swap steps, because an extra swap adds another price and execution risk.

What Happens After You Sign?

The Jumper crypto bridge sends the chosen route for execution after you authorize the required source-chain transaction. LI.FI contracts perform any source swap and call the selected bridge. The bridge moves value across chains; a destination swap then converts the received token when the route calls for one. LI.FI’s contract documentation describes its bridge and DEX aggregation.

Those steps form one route, but cross-chain execution is not atomic: a completed bridge transfer cannot be rolled back because a later swap fails. The source transaction can finish while delivery or destination execution is still pending. Read the route as a sequence of obligations, with a different protocol responsible at each stage.

Why Do Routes Arrive at Different Times?

A Jumper cross-chain route inherits the delivery model of its underlying bridge. Hold the source token, amount, destination token and slippage tolerance fixed, and change only the bridge. With Across Protocol, a relayer can front destination funds to fill the user’s intent; the relayer is repaid later through bundles secured by UMA’s optimistic oracle. User delivery can therefore precede relayer settlement.

With Stargate Finance, value moves through pooled liquidity and LayerZero messaging. Delivery depends on source-chain confirmation and verification of the cross-chain message. The two routes may quote similar output yet expose you to different waits and security assumptions. Apply that same inspection to any other bridge route, including Mayan: route choice is also a bridge security choice.

What If the Final Swap Fails?

A Jumper cross-chain route can finish with the intermediate bridged token if the destination swap exceeds your slippage tolerance or lacks sufficient liquidity. Say the bridge delivers USDC but the planned swap into your target token cannot meet its minimum output. The bridge leg has succeeded; the target-token leg has not. LI.FI describes this as a partial completion.

Look for the bridged token on the destination chain before treating the transfer as missing. You can swap that token manually when liquidity and price suit you, accounting for another transaction and its gas. Before signing any route, decide whether its likely arrival time, underlying bridge and possible intermediate token are acceptable for the amount you are moving.

Subscribe to How to Restake Stablecoins and LSTs