Jumperexchange

Jumperexchange swaps and bridges across supported chains

Jumperexchange compares swap and bridge routes so users can exchange tokens on one blockchain or move assets between supported blockchains. Its routing combines available exchanges and bridges, while gas, liquidity, and the selected path affect cost and execution. The app also includes gas refueling, fiat purchase access, and DeFi tools.

Updated
The short version: A route’s destination token, fee deductions, and gas requirements determine whether it suits the intended transfer or swap.

The destination network determines the route

The selected source and destination networks determine whether a request stays within one chain or needs cross-chain execution. The input asset and amount then shape the available paths.

Same-chain swaps

A same-chain swap exchanges the input token for another token on the same network. Jumper compares quotes from multiple decentralized exchange aggregators, which search available trading liquidity. A decentralized exchange, or DEX, executes token trades through blockchain contracts. The available liquidity affects both pricing and the amount that a route can handle.

Bridging and cross-chain swaps

A bridge transfers value between networks, while a cross-chain swap also changes the asset along the route. Conversion can happen before bridging, after bridging, or at both ends when the chosen path requires it. Some routes combine operations within a transaction; others require a separate destination transaction. The number of conceptual operations therefore does not establish how many wallet confirmations a particular route needs.


Routing through exchange aggregators and solvers

Jumper combines quotes from supported routing providers to offer different ways of reaching the requested destination asset. Exchange aggregation searches trading liquidity, and bridge aggregation compares available transfer paths. A route can connect these functions when the requested asset requires conversion during a cross-chain transfer. These functions let the app handle both local trading and movement between networks within one interface.

Intent-based routes add another execution model. Jumper added support for same-chain and cross-chain Intents routes in May 2026. An intent specifies the desired outcome, and solvers compete to fulfill it. A solver takes responsibility for the execution path that satisfies that request. Supported assets and networks determine where this model applies; its presence does not impose identical execution mechanics on every route.

Visual outline: Jumperexchange - Routing through exchange aggregators and solvers

View image file


Route costs and execution quality

A route’s economic outcome reflects its exchange pricing, provider charges, and network costs. Comparing routes requires the same input amount and requested destination asset.

Gas and provider charges

Gas pays for blockchain execution, while bridges and trading providers can charge for their own services. For a conventional bridge transaction, the sender pays source-chain gas. The bridge can deduct fees from the transferred tokens to fund destination execution. A separate destination transaction can introduce another wallet-funded gas requirement. Fee deductions and gas payments therefore need their own interpretation: some reduce the transferred amount, while others draw on a native-token balance.

Quoted output and minimum output

Quoted output estimates the destination amount for the selected route. Minimum output describes the floor that the execution settings allow. A swap can revert if it cannot meet that floor. Price impact measures the trade’s own effect on execution pricing, while slippage concerns changes between quoted and executed amounts. Increasing a slippage allowance permits a worse execution outcome; it does not improve the underlying exchange price. A displayed estimate and an actual received balance describe different stages of the trade.


Wallet permissions and destination settlement

Wallet authorization permits the selected contracts to act, and settlement establishes what the route actually delivered. An ERC-20 token approval gives a specified spender permission to use that token within its allowance. A route may require approval before execution, depending on the token and existing permissions. Native-asset transfers use a different mechanism and do not require an ERC-20 approval for the native asset. The requested spender and amount determine the permission’s scope.

A successful source-chain transaction establishes execution on that chain. A cross-chain route can still await bridge settlement or a destination operation afterward. Where a destination swap fails after bridging, the route may deliver an intermediate asset. The destination transaction and received token balance distinguish completed conversion from that fallback. A transaction identifier alone does not describe the final asset that the recipient holds.


Native gas through LI.Fuel

LI.Fuel provides access to native gas tokens on supported chains, addressing the difference between holding a traded token and holding transaction fuel. Jumper introduced the feature in 2023. Where a route offers destination refueling, part of the selected input can fund a native-token amount on the receiving chain. That allocation serves later network activity and changes how much value remains for the main destination asset. Refueling availability belongs to the selected route, and its cost belongs in that route’s quote.

Fiat purchases through Onramper

Onramper aggregates fiat-to-crypto providers, giving Jumper users access to purchases with supported currencies and payment methods. The app added this integration in 2023. This path differs from exchanging tokens that a wallet already holds: a provider processes a payment and delivers cryptocurrency. Available currencies, payment methods, assets, and countries depend on the selected provider. Its purchase terms also determine transaction limits and processing requirements.

An onramp checkout may request identity and payment information. Know Your Customer, or KYC, checks belong to the purchase service and its applicable requirements. Some verification services allow reuse of identity information across selected providers. That feature has its own consent and data-sharing conditions. A provider’s verification or payment requirement should not be generalized into a rule for every blockchain swap in the app.


Dust Sweeper, Earn, and portfolio positions

Dust Sweeper consolidates small token balances, while Earn connects supported assets with DeFi opportunities and portfolio tracking. These functions extend the app beyond individual swap requests.

Dust Sweeper

Dust Sweeper uses Composer to convert selected low-value balances into the native asset of the selected chain. Composer coordinates multiple token inputs and their swaps within a consolidated execution. Newly selected tokens can require approvals before the first sweep. Persistent allowances can reduce repeat approvals later. When a token cannot be routed, the feature can omit that operation and ask for confirmation of the revised selection. Consolidation therefore applies to the tokens that the resulting execution can actually handle.

Earn and portfolio tracking

Jumper Earn brings yield discovery, comparison, and deposit execution into the app. Its infrastructure combines vault information with the routing needed for supported deposits. Jumper Portfolio provides a cross-chain view of positions and supports position management. Historical annual percentage yield, or APY, expresses an annualized rate drawn from the displayed historical period. A routed deposit still follows the selected vault’s underlying strategy and withdrawal rules. Swapping into an asset and placing it into a yield position also create different exposures.

Network coverage and live route availability

Jumper’s network integrations support specific combinations of transfers and local trading. Robinhood Chain support included bridging into and out of the network, plus same-chain swaps, in July 2026.

By September 2026, Jumper also supported movement between Stellar and other supported ecosystems and trading assets native to Stellar. This extends the network coverage beyond one blockchain architecture. Each available path still requires compatible assets and sufficient routing liquidity.

A listed network describes connectivity. The input amount, provider availability, and route settings determine whether a usable quote exists for a particular request.


Does the archived frontend repository mean Jumper has closed?

Jumper remains live and supported despite the archival of its public frontend code. The public Jumper frontend repository entered archival status on July 23, 2026. Development moved to a private repository. The archived code reflects the app at the time of that change and no longer receives updates, fixes, or support. Its maintainers also stopped monitoring issues and pull requests there. The archive notice concerns that codebase and its maintenance channel.


Choosing a route for the intended destination

A local swap keeps the resulting asset on the starting chain. Moving value to another network requires a cross-chain path, with settlement and provider conditions that also enter the comparison. Use the requested destination to decide which quoted results are relevant.

  • Keep the source asset and amount consistent when comparing quotes for the same request.
  • Match the output token, destination network, and receiving address to the intended use.
  • Account for fee deductions, separately paid gas, and any value allocated to destination refueling.
  • Inspect the minimum output and any approval or separate destination transaction that the selected route requires.
  • Treat duration as an estimate for the chosen path, including its bridge and destination execution.

Changing the amount, destination, or route settings can change the available quote. A comparison applies while those inputs and execution conditions remain consistent.

Jumperexchange: questions and answers

How long does a cross-chain transfer take?

Transfer time depends on source confirmations, the selected bridge’s settlement process, and any destination execution. A route’s duration estimate applies to that path. The time needed to retrieve a quote measures a separate process and cannot establish delivery time. A successful source transaction can precede receipt on the destination chain.

What does a DONE/PARTIAL transfer result mean?

A DONE status with a PARTIAL substatus indicates that the route’s outcome did not fully match the requested destination result. One cause is a completed bridge followed by a destination swap that could not execute. The recipient may hold an intermediate token. The actual destination token, amount, and transaction state explain what remains unresolved.

Which token address should I use when an asset is missing from search?

Use the intended token’s contract address on the selected network to distinguish it from assets with similar names. Jumper can search for tokens by address even when its default list omits them. A search result identifies the token; available liquidity and routing support determine whether a trade can proceed.

Can a successful simulation guarantee completion of a bridge route?

A successful simulation checks the transaction behavior that the simulation can reproduce. It cannot fully reproduce asynchronous bridge settlement, external relayers, or later destination conditions. A simulated source transaction therefore provides a different kind of evidence from an executed destination transfer. Completion requires the relevant on-chain result.

Does disconnecting my wallet remove an ERC-20 token approval?

Disconnecting a wallet does not revoke an existing on-chain ERC-20 allowance. The approved spender retains the permission that the token contract records until spending or an allowance update changes it. Revocation changes that contract state through a transaction. Wallet connection permissions and token spending permissions have separate scopes.

When should I contact the provider about a delayed fiat purchase?

Contact the selected onramp provider when a purchase exceeds its stated processing window or requires help with payment or identity verification. That provider handles the purchase, and its order record identifies the relevant service. A blockchain transaction record alone may not explain a payment that has not reached the delivery stage.

Are routes in an embedded swap widget identical to those in Jumperexchange?

An embedded widget can apply different route settings from the Jumper app. Provider filters, permitted execution paths, and price-impact thresholds can change the options that an integration displays. Sharing routing infrastructure therefore does not establish an identical route list. Compare equivalent inputs and settings before interpreting a difference.

Is a smart-contract wallet eligible to receive every available route?

Destination support depends on the selected bridge and its implementation. Some bridge methods exclude smart-contract receiving addresses, even when their destination network is supported. Network compatibility and recipient compatibility are separate requirements. The route must support the intended account type before a source transaction can safely target that address.