Jumper: cross-chain routing, partial outputs and the announced company expansion

Jumper provides a swap interface linking wallets and aggregating available routes across decentralised exchanges and cross-chain infrastructure. A user chooses the origin chain, token, output asset and receiving chain; the displayed estimate may select a bridge and one or more token swaps. A cross-chain “exchange” in this sense is not the same service as a custodial BTC/USD order book: there is no ordinary account deposit ledger or guarantee of continuous execution at an advertised bid.[1][5]

The September 2026 announcement describes Jumper spinning out to develop an independent product. It cites commercial lifetime activity and monthly usage, but those are company-supplied metrics rather than independently audited exchange-user counts. The spinout is also a reason not to assume every LI.FI company legal permission, liability or contractual term is automatically the legal status of Jumper itself.[2][6]

No independently verified universal “Jumper charges X% per transaction” tariff applies to every path in the reviewed documents. Relevant costs may include protocol swap fees, bridge/relayer fees, origin-chain network gas, destination execution gas, any integrator charge and the price impact caused by low liquidity. The quote and transaction payload for the *particular* route are the key evidence. Not every component is charged in the source token or immediately visible as a standalone debit.[1][5][6]

A hypothetical $1,000 start with a $990 net output valued at parity illustrates a 1.0% all-in shortfall, not a claimed fixed Jumper fee: (1,000−990)/1,000. That difference could contain slippage, protocol fees and intermediary gas. If the two assets differ in price, one cannot subtract token counts to compute a monetary percentage; use a consistent timestamp and price basis before comparing quotes.[5][3]

The workflow begins with assets already held in a compatible wallet. A token approval may authorize a spender before a second signature transmits value; the approval itself is not proof that the swap happened. Source-chain gas, correct wallet chain, remaining token allowance, route availability and quote expiry all matter. There is no evidence of a generally available direct ACH, card or TRY deposit account supplied by the Jumper routing interface itself.[1][5]

A route can reach the destination as a transit or intermediate asset when its final destination swap cannot execute, rather than returning the expected coin. LI.FI labels some cases DONE with PARTIAL execution or REFUNDED and explains that recovery cannot simply assume an instant source-asset repayment. Support must first inspect source/destination transaction hashes and the route status.[3][4]

The connected wallet holds the assets before a signed transaction, so Jumper cannot be treated as a conventional custodial exchange safeguarding an omnibus customer balance. Once assets enter route contracts, bridge systems, liquidity providers or relayers, specific smart-contract and operational risks apply. The phrase “non-custodial” does not eliminate the possibility of funds being delayed or an exploitable approval remaining in place after the transaction.[1][3]

A user should limit token approvals where possible, verify destination addresses and use official chain explorers to confirm both legs. The audited status of one module, if any, does not establish that every token or bridge in every quote has been independently audited or insured. Tokens with unusual transfer mechanics and wrapped assets add further execution differences beyond the visible UI.[7][3]

A route can be accessible without opening a traditional identity-verified exchange account, but on-chain reachability is not legal permission. Country restrictions, sanctions exposure, locally prohibited derivatives or token offerings and third-party protocol terms can still block participation. A supported chain does not mean every token is eligible: LI.FI documents token-listing and support decisions, including that not every asset visible on a blockchain is available in its services.[7][6]

Some wallet permissions and API terms are aimed at integrators, not normal retail users. Enterprise rate limits, commercial access clauses and compliance representations should not be silently treated as the Jumper retail wallet contract, especially after the 2026 spinout. The exact user agreement should be inspected again at accountless swap execution.[2][6]

Recovery begins with an ordered event record: sending wallet, origin chain ID, input token, route quote, source hash, destination address, destination transaction or bridge identifier, and output token address. A wallet screenshot or an “in progress” banner alone may not show whether the underlying route has completed. LI.FI guides describe PENDING, DONE, PARTIAL and REFUNDED states, each requiring different investigation.[3][4]

If the final swap fails after the bridge succeeds, the wallet can hold a bridge asset rather than the requested token. Simply repeating the swap could spend more gas or move a token that was already delivered; verify the actual destination balances first. The source documentation does not promise that every loss, expired quote or wrong-chain transfer is reversible by Jumper support.[3][4]

The 2026 Jumper spinout announcement means naming the LI.FI API as technical infrastructure is not enough to name the present general-purpose contracting company for every Jumper user. The reviewed material did not establish a single verified statutory exchange authorisation, company registration/permission number or covered-client compensation regime for this user-facing routing service. No positive regulated-permission record is entered.[2][6]

LI.FI commercial API terms impose responsibilities on integrators and constraints on automated execution. Such contractual safeguards are distinct from government exchange licensing. A token or bridge contract being open-source, audited or integrated by a popular app does not turn the exchange front end into a regulated custodian.[6][5]

Jumper’s September 2026 announced spinout marks a meaningful distinction from its earlier positioning as a LI.FI-related consumer routing frontend. The announcement describes the intention to build a wider on-chain application and refers to cumulative activity and monthly users. Those figures are self-reported in launch communications; wallet transactions, repeat swaps, activity through aggregators and human registration do not produce identical user counts.[2]

The interface is active at jumper.xyz in the reviewed evidence. An accurate company profile must distinguish the frontend brand, the backend routing infrastructure and the legal entity responsible for any quote or API interaction. A universally applicable contracting entity for all users and a detailed independently verified current audited balance sheet were not established.[1][2][6]

Operator

Jumper interface (independent product; all-user contracting entity not independently identified)

Exchange model

Decentralised

Service scope

Wallet-connected cross-chain routing and token swapping across supported chains using underlying DEX and bridge liquidity; not a custodial central limit order book.

Client types

Retail clients; Institutional clients

Pricing publication

Public and quoted pricing

Other names

Jumper; Jumper.xyz; LI.FI Jumper

Pricing scope

Protocol, pool, bridge and gas costs vary per route; this is not a fixed order-book commission. Always check minimum received and transaction approvals.

Funding scope

No standard cash ledger or bank deposit. Fund a supported wallet with source-chain tokens and required gas. Destination funds depend on execution and finality of all route legs.

Custody and asset handling

The user generally signs from a self-custody wallet but tokens can be committed to third-party routers, pools or bridging escrows; operator of each leg must be examined separately.

Client eligibility

Wallet and chain/network access, applicable sanctions and interface terms; supported tokens/routes vary and a working web app is not evidence of lawful availability everywhere.

Support

Transaction tracking and LI.FI technical support routes when its routing is used. Token delivery, bridge refunds and additional destination leg may differ from quote.

Authorisation and registration scope

No entity-specific regulated centralised exchange licence or deposit protection substantiated for Jumper; September 2026 spinout announcement further limits blanket attribution to LI.FI entities.

Exchange metadata checked 26 Oct 2026Source 1Source 2Source 3Source 4Source 5Source 6Source 7

Compare two routes using a common value unit, input token decimals, the exact output-token contract, quoted minimum, gas budget and chain finality. If the route is complex, a lower advertised bridge charge can still produce a worse net output after DEX slippage and destination-gas effects. The smallest fee in a table is not an instruction to pick the smallest liquidity pool without examining the eventual received amount.[5][3]

Automated agents consuming LI.FI endpoints should enforce route/token allowlists, destination address rules, maximum trade sizes, gas/slippage ceilings and human review for material transactions. The published API commercial terms discuss user responsibility and limits; neither AI-generated trade proposals nor a successful simulation authorise an unattended bot to sign arbitrary wallet transactions. No live trade or wallet integration was tested in this research.[6][5]