Jumper tutorial is an Educational Resource for Safer Cross-Chain Signing

Jumper Route Preview Versus a Direct Across Transfer

A Jumper route preview is an aggregator-level execution plan that combines available swaps and bridges, while a direct Across transfer presents one bridge protocol’s own path.

Jumper’s preview reflects the LI FI aggregator search and names the bridge, any decentralized exchange or solver, estimated gas, provider fees, expected duration, conversion rate, and quoted output. A direct Across transfer starts and ends within Across’s intent-based bridge workflow, so there are fewer composed stages to reconcile. This Jumper tutorial uses that contrast to frame the preview’s purpose: it explains the selected path before the wallet receives executable transaction data.

Use Jumper to compare composed paths; choose a direct provider when you’ve already selected its route mechanics, such as Across.

The Five Fields to Match Before Signing

The pre-signing field match is a five-part identity check that aligns the source asset, destination asset, recipient, quoted output, and selected LI FI route with your intent.

Source Chain and Spend Token

Start with the asset that leaves your wallet.

The source chain controls which wallet network pays gas and which balance Jumper reads. Match the source ticker, token contract for an ERC-20, and entered amount. A native ETH route carries value in the transaction, while a USDC route calls a token contract. The connected account needs the spend token and the source network’s native gas asset. A Base balance doesn’t fund an Arbitrum One transaction, although both networks use ETH for gas. If the input changes, let LI FI recalculate the path.

Recipient and Destination Token

The recipient field determines where the completed route delivers its output. When the connected wallet is also the recipient, both addresses should match exactly. A different recipient requires deliberate review because Jumper sends the destination token there, not back to the connected account. Match the destination chain, ticker, token contract, and recipient together; those four values define the delivery target.

Output and Route Components

The output block identifies the expected amount, any enforced minimum, and the protocols that form the path. A route can include a Uniswap swap before a Stargate bridge, for example, while another route uses Across without a separate destination swap. Read the stages in order. The quoted output describes the selected route, so changing the bridge, token, recipient, or amount requires a newly reviewed LI FI route.

Allowance Prompts and Transfer Prompts

An ERC-20 authorization sequence is a two-layer signing workflow whenever the chosen spender lacks sufficient allowance: approve token access first, then authorize the route’s main contract call.

ERC-20 Allowance

An approval sets the spender and allowance amount; it doesn’t deliver the destination token. Compare the wallet’s spender with the route’s approval target, and read whether the request covers the exact input or a larger limit. An EVM account or contract address contains 20 bytes, rendered as 40 hexadecimal characters plus the 0x prefix for 42 characters total. Address length confirms the format, while the full character sequence identifies the actual spender. Further detail lives in Jumper what are alternatives in practice.

Main Route Transaction

The main transaction starts the swap, bridge, or composed route after allowance exists. A LI FI quote represents one route step, while an advanced route holds one or more ordered steps. An ERC-20 step can still produce an approval transaction followed by its main call. Match the wallet’s network, contract target, token amount, and native gas estimate with the currently displayed route.

Native Asset Calls

Native ETH skips the ERC-20 allowance prompt, leaving the route contract call and its network fee for review. The wallet’s value field then carries the routed ETH amount, while a separate gas estimate covers execution. Zero approval prompts are expected for native ETH, but wrapped WETH remains an ERC-20 and follows the allowance workflow.

Chain IDs That Anchor the Destination Check

An EIP-155 chain ID is a network identity constraint that distinguishes similarly named EVM environments and ties each wallet signature to the intended blockchain.

Ethereum Mainnet uses chain ID 1, Optimism uses 10, Arbitrum One uses 42161, and Base uses 8453.

A route from Arbitrum One to Base begins with the wallet on chain ID 42161. If the path includes a destination-side transaction, the later prompt switches to chain ID 8453. MetaMask and Rabby commonly present network names more prominently than numbers, yet the numeric identity remains part of the transaction context. Review each switch against the corresponding route stage, ending on Base chain ID 8453.

Quoted Output, Minimum Output, and Slippage

A Jumper output panel is a quote-boundary display that separates the expected destination amount from any minimum amount enforced by a swap’s slippage setting before signing. One basis point equals 0.01%, and a 0.5% tolerance equals 50 basis points. Price impact reflects how the trade interacts with available liquidity; slippage tolerance defines acceptable movement after calculation. Bridge charges, provider fees, and gas belong to separate cost components. The minimum output, rather than the estimate alone, defines the swap’s enforceable boundary at 50 basis points.

What Changes When a Quote Refreshes?

A refreshed Jumper quote is a newly calculated route proposal that can change the expected output, minimum output, provider sequence, gas estimate, and approval target before execution.

Refreshes are decision points because LI FI generates executable calls from the updated route.

Recheck the source amount, destination token, recipient, minimum output, and named protocols after every refresh. Liquidity movement can replace a decentralized exchange or bridge, which also changes the contracts that receive approvals and route calls. An allowance granted for the previous spender doesn’t automatically cover the replacement. Likewise, an older wallet prompt no longer represents the route now visible in Jumper, even when the input and destination tickers remain unchanged.

Discard the earlier prompt and reopen the current preview when its components diverge, whether the new path selects Across, Uniswap, or Stargate.

Token Identity Beyond the Ticker

A destination-token identity is the combination of blockchain, contract or mint, ticker, and decimal precision that tells the route exactly which asset representation to deliver (set out in practice ).

USDC uses 6 decimal places, so 1 USDC is encoded as 1,000,000 base units on its supported EVM deployments. WETH9 uses 18 decimal places, making 1 WETH equal to 10^18 base units.

Those units matter because route APIs and contract calls encode integers, while Jumper renders human-readable amounts. Native ETH has no ERC-20 token contract, whereas WETH represents ether through an ERC-20 contract. Two assets can share a familiar ticker while using different contracts or issuance mechanisms. The destination row therefore needs agreement across chain, contract, decimals, and symbol. Reviewing only the symbol leaves the route’s actual asset identity unresolved.

Mechanism also distinguishes routes. Circle CCTP burns native USDC on the source chain and mints native USDC on the destination, while liquidity bridges use their own settlement flow. The preview identifies the selected path and final representation, including Circle CCTP.

Gas, Provider Fees, and Route Cost Drivers

A Jumper cost preview is a layered estimate that separates source-chain execution, integrated protocol charges, swap price impact, and any destination-gas conversion included in the route.

Source Network Gas

Source gas uses that chain’s native asset. On Ethereum, Arbitrum One, Optimism, and Base, the wallet pays ETH even when the input token is USDC. One gwei equals 10^9 wei, while 1 ETH equals 10^18 wei. An EIP-1559 wallet expresses execution through a maximum fee and priority fee per gas. Rollup estimates also account for their network-specific data-cost model.

Bridge and Swap Costs

LI FI documents a 0.25% service fee for each transaction, and the route preview adds costs from the selected bridge or exchange. Across derives its transfer cost from the difference between input and output, including liquidity-provider and relayer components. A Stargate route follows Stargate’s fee mechanics, while a Uniswap step includes the fee that the chosen pool charges and the trade’s price impact. The quoted output consolidates these route-specific effects.

Destination Gas Conversion

Some routes offer a destination-gas amount through LI Fuel, using part of the input to deliver the destination chain’s native asset. Review that amount as another output component, not free gas. If no destination-gas line appears, the route delivers only its stated token output. The wallet still prices the source transaction in units such as 1 gwei.

Route Status and Destination Verification

A route-status record is the post-signing execution trail that connects the source transaction, selected bridge, intermediate steps, and final destination-chain balance.

Record the source transaction hash, bridge name, source chain, destination chain, recipient, and output token after submission. An EVM transaction hash contains 32 bytes, displayed as 64 hexadecimal characters plus the 0x prefix for 66 characters total. Jumper Scan follows the route beyond that initial hash and associates later execution stages with the transfer. A bridge fill or destination swap can create another transaction record, so the source receipt alone doesn’t establish that the final token reached the recipient.

Check the destination balance against the token contract named in the preview. A wallet can omit an unfamiliar token from its default asset list even when the on-chain balance exists. Adding that contract to the wallet changes visibility, not ownership. For a multi-step route, wait for Jumper Scan to mark each ordered stage complete before treating the quoted workflow as settled.

A Base receipt on chain ID 8453 closes the review loop.

User Fit for Preview-Led Cross-Chain Signing

A preview-led Jumper workflow is a cross-chain execution method for users who value route choice, destination-token precision, and visible protocol composition before authorizing wallet calls. It fits transfers that combine a source swap, bridge, and destination swap, especially when the final asset matters more than merely reaching another network. Hardware-wallet users also gain a broader route context around the device prompt. When the bridge provider and destination asset are already fixed, a direct transfer offers a narrower review surface through a protocol such as Across.