A Uniswap crosschain swap can turn a source-chain asset into a different destination-chain asset through one interface, but the result still depends on several verifiable events. A quote must be accepted, the source transaction must settle, Across must fulfill the intent, and the correct token must reach the correct address on the destination network. This guide builds an audit trail for that entire route so you can measure the real cost, prove delivery and respond safely when the transfer appears delayed or incomplete.

Last reviewed: October 24, 2026. Supported networks, tokens, routes, fees, interface labels and Across availability can change. Treat the live Uniswap quote, wallet request and verified onchain records as controlling information. This independent guide is educational and is not financial, legal, tax or investment advice.

Quick answer: before signing, record the source and destination networks, both token contracts, input, estimated output, minimum output, route, fees and approval spender. After signing, preserve the source hash and follow the status in Uniswap Activity and the official Across explorer. A completed source transaction proves only that the source-side call succeeded; destination delivery must be confirmed independently through the correct destination address, token contract and transaction. If one stage fails, use the retry or recovery action attached to that route instead of creating a duplicate swap.

What a Uniswap crosschain swap actually does

A same-chain swap exchanges assets inside one blockchain environment. A crosschain swap starts with value on one network and delivers value on another. Uniswap presents the route as one coordinated flow, while the underlying process can include token authorization, a source-chain call, crosschain intent fulfillment and a destination-side swap or transfer.

Uniswap says its current crosschain swaps combine Uniswap routing with the Across bridge. Across uses an intent-based design: the user defines the desired outcome, a filler supplies the destination assets, and the protocol verifies fulfillment before the filler is repaid. This can feel faster and simpler than manually bridging and then swapping, but it does not remove contract, liquidity, network or token risk.

Crosschain swap, bridge and network switch are different

Action What changes Typical result What it does not prove
Network switch Only the network shown in the wallet The same account viewed on another chain No asset was moved
Same-chain swap Token Token A becomes token B on one network No crosschain delivery occurred
Bridge Network An asset or its supported representation arrives on another network The asset may not have been exchanged
Crosschain swap Network and potentially token Token A on the source becomes token B on the destination Every stage is not one atomic blockchain transaction

Switching from Ethereum to Base in a wallet does not move ETH. Likewise, seeing a successful transaction on Ethereum does not by itself prove that USDC arrived on Base. Each statement requires its own evidence.

The five records in a complete audit trail

  1. Quote record: the proposed input, output, networks, token contracts, fee information, route and expiry.
  2. Authorization record: the approval or Permit2 permission, including spender, token, amount and network.
  3. Source transaction: the transaction hash, sender, called contract, amount, status and emitted events.
  4. Fulfillment record: the Across order or deposit and the filler delivery status.
  5. Destination proof: the destination transaction, recipient, token contract and final balance change.

Keep these records until the route is reconciled. A screenshot is helpful for the quote, but transaction hashes and explorer data are stronger evidence for what actually happened.

Who does what in the route?

Component Role Main question
Uniswap interface Builds and displays the user flow Am I on the official application and reviewing the intended route?
Uniswap routing Finds eligible swap liquidity What route and final output are quoted?
Wallet Controls the account and signing authority What exact permission or transaction am I authorizing?
Source chain Records the initial authorization and execution Did the source transaction confirm successfully?
Across Coordinates intent-based crosschain fulfillment Was the order filled, delayed, failed or refunded?
Filler Supplies the requested destination assets Was the requested output delivered before the deadline?
Destination chain Records delivery and any destination execution Did the correct recipient receive the correct token?

What is a crosschain intent?

An intent describes the outcome the user wants instead of requiring the user to construct every intermediate action. The intent can specify the source input, destination output, recipient and deadline. Fillers compete or respond to deliver that outcome, while settlement logic verifies whether the conditions were satisfied.

This distinction matters during troubleshooting. You are not merely waiting for a token to travel through an invisible tunnel. You are checking whether an order was created, whether a filler delivered the specified output and whether settlement recognized the delivery.

What a filler is—and is not

A filler provides destination liquidity to satisfy an intent and is later repaid under the protocol’s rules. Fast delivery can therefore occur before a slow canonical movement of capital would finish. A filler is not customer support, does not need your recovery phrase and should never ask you to sign an unrelated “release” or “validation” transaction through direct messages.

The official interface and explorers should provide the useful identifiers. Anyone claiming that a delayed fill requires a private key, seed phrase, remote-access session or deposit to a recovery address is attempting to steal funds.

Verify the official entry point

Open the Uniswap application through a trusted bookmark or the official Uniswap website. Check the complete hostname, not only the logo or page design. Search advertisements, lookalike domains and unsolicited support links are common attack paths.

  • Never enter a recovery phrase into a swap website.
  • Do not install a browser extension suggested by a support message.
  • Do not trust a route simply because it uses the Uniswap name.
  • Confirm that the wallet request originated from the tab you intended to use.

Verify the account and recipient

The connected source account may also be the destination recipient, but do not assume that every route uses the same address automatically. Record the full recipient address shown in the route or transaction details. This is especially important when using smart accounts, embedded wallets, hardware-wallet accounts or an address that differs across ecosystems.

For EVM-to-EVM routes, the hexadecimal address format may look familiar across chains, yet balances and contracts remain chain-specific. A matching address string does not merge the networks.

Verify both networks before both tokens

Start with the source network where the asset currently exists and then choose the intended destination. A token symbol without its network is incomplete information. “USDC” on Ethereum and “USDC” on Base are separate contract balances even when they represent the same issuer’s asset.

Confirm the network in three places: the Uniswap selectors, the wallet confirmation and the relevant explorer. If those views disagree, stop before signing.

Supported crosschain networks

At this review date, Uniswap’s dedicated crosschain support page lists Ethereum, Unichain, Arbitrum, Base, Ink, Linea, MegaETH, Monad, Optimism, Robinhood Chain, Soneium, World Chain, ZKsync and Zora. It lists Arc, Avalanche, BNB Smart Chain, Celo, Polygon, Solana, Tempo and X Layer as unavailable for this feature.

This is not the same as the broader list of networks where Uniswap products or protocol deployments exist. A network may support ordinary swaps without supporting the current crosschain-swap product. Availability can also depend on the token, amount, direction and live filler liquidity. A valid quote in the official interface is the transaction-specific check.

Verify source and destination token contracts

Token symbols and logos are not unique. Open each asset’s details and compare the contract with an authoritative source or the issuer’s verified listing. Check decimals and token representation as well. Bridged, wrapped and native versions can have similar names but different contracts and redemption properties.

Record:

  • source network and token contract;
  • destination network and token contract;
  • input amount and expected output;
  • recipient address;
  • minimum acceptable output or protection terms.

Capture the quote before it expires

A quote is an estimate under current prices, liquidity, gas and filler conditions. It can change when you wait, edit the amount or switch networks. Before signing, capture the quote details rather than relying on a headline conversion rate.

Quote field Why it matters
Input and output Defines the economic exchange you expect
Source and destination Prevents a network-direction mistake
Minimum output Shows the protected lower bound where applicable
Route Identifies crosschain and swap components
Estimated time Creates a reasonable monitoring window, not a guarantee
Fees and network costs Supports comparison with alternatives
Price impact Shows liquidity-related deterioration
Expiry or deadline Defines when the offered conditions stop applying

Approval, Permit2 and execution are separate

An ERC-20 approval gives a spender permission to use tokens; it does not itself perform the crosschain swap. Depending on the route and previous permissions, the wallet may request an approval, a Permit2 signature and an execution transaction. Read each request independently.

For an approval, verify the network, token, spender and amount. For a signature, verify the domain, token, amount, spender and deadline. For execution, verify the called contract and expected asset movement. A familiar first step does not make a later request safe.

How to measure the real crosschain cost

The real cost is the difference between a reasonable source value and the destination value actually received, adjusted for unavoidable network costs. Do not judge a route by one fee label.

Cost Where it appears How to evaluate it
Source gas Approval and execution on the source chain Check the wallet estimate and final receipt
Across/filler fee Included in the crosschain quote Compare input with delivered output and quote details
Pool or execution fee Reflected in the swap route Review route and final output
Price impact Quote deterioration caused by available liquidity Compare smaller sizes and alternative timing
Slippage or quote movement Difference between expected and protected execution Review minimum output and final transfers
Destination gas reserve Not necessarily provided with the received token Check whether later actions require native gas

Across fee versus Uniswap interface fee

Uniswap’s Across support material says the displayed crosschain quote includes a fee paid to the relayers and liquidity providers that power Across, and that neither Across Protocol nor Uniswap receives that particular fee. This statement should not be generalized to every other possible fee, route or future product setting. Read the live breakdown and compare the final destination amount.

Compare final output, not percentages

To compare a crosschain swap with a manual bridge followed by a swap, normalize the outcome:

  1. Use the same source input and destination asset.
  2. Include every approval and source transaction.
  3. Include bridge and swap costs.
  4. Include price impact and protected minimum output.
  5. Consider time, extra signatures and operational risk.
  6. Compare the destination amount that can actually be used.

A manual route may display a lower bridge fee but require another swap, another approval and destination gas. A one-flow route can be operationally simpler without always being economically best.

Keep native gas on the source network

If the source asset is also the native gas asset, avoid committing the entire balance. The wallet needs enough for the source call and possibly an approval transaction for other tokens. Gas estimates can move between quote and inclusion.

Receiving an ERC-20 token on the destination network does not necessarily give you its native gas token. Plan how a later transfer or approval will be funded without accepting unsolicited “gas assistance.”

Sign only after the quote and wallet agree

The wallet is the final authorization surface. Compare its network, account, contract, value and simulation with the quote. Cancel if the wallet shows an unexplained recipient, unlimited permission, different network or unexpected asset transfer.

After broadcasting, save the source transaction hash immediately. Do not repeatedly click confirm because the interface is slow; check the wallet activity and explorer first.

Audit the source transaction

Open the hash in the correct source-chain explorer and verify:

  • transaction status is successful;
  • sender matches your source account;
  • called contract matches the expected route;
  • native value and token transfers match the intended input;
  • approval was not mistaken for execution;
  • block confirmations are progressing;
  • events contain identifiers needed for crosschain tracking.

If only an approval succeeded, the crosschain operation may not have started. If execution reverted, no successful fulfillment should be inferred from the failed call.

Track fulfillment through official activity

Use Uniswap Activity to find the combined route status. When closer inspection is needed, follow the route into the official Across explorer using the provided transaction or order identifier. Avoid copying a hash into a random “crosschain checker” promoted in search results.

A route can pass through states such as submitted, source confirmed, pending fulfillment, filled, completed, failed or refunded. Exact labels may change, so interpret the evidence rather than depending only on color or icon.

What destination proof looks like

A strong destination proof connects the destination transaction to the correct recipient and token contract. Check the destination explorer for:

  • successful transaction status;
  • correct destination network;
  • recipient address matching the route;
  • correct destination token contract;
  • delivered amount consistent with the quoted protection;
  • transfer logs and balance change.

The wallet UI may lag or hide an unfamiliar asset. Explorer evidence can show successful delivery even before the portfolio view refreshes.

Why received tokens may not appear

First confirm that the wallet is viewing the destination network and the intended account. Then verify the token contract. The wallet may require the asset to be imported manually, or it may group multichain balances in a way that hides the per-network location.

Do not import a token contract from a stranger. Obtain the destination contract from the route, verified explorer entry, issuer documentation or official token list. A fake token with the same symbol can create a misleading balance.

Status matrix: what to do next

Observed state Meaning Safe next action
Approval confirmed, no execution hash Permission exists but swap may not have started Return to official activity and verify whether execution still requires confirmation
Source transaction pending Source chain has not finalized the call Monitor the same hash; do not launch a second route
Source transaction reverted Execution failed on source Read the error and verify token, allowance, balance, gas and quote expiry
Source succeeded, fulfillment pending Across delivery is not yet complete Track the official order and allow the stated processing window
Destination transaction succeeded Onchain delivery occurred Verify recipient, token contract and wallet display
Route offers Retry An intermediate stage needs a new action Use the retry attached to the original activity after reviewing the new wallet request
Refund recorded Value returned under route rules Verify refund network, token, recipient and amount before considering a new swap
No recognized order Wrong hash, wrong network or execution never started Recheck the approval/execution distinction and source explorer

Retry is not the same as restart

Uniswap’s troubleshooting guidance says a failed intermediate step may present a retry from the failure point. That is different from creating a fresh crosschain quote and paying again. A fresh route can execute in addition to the original if the first operation later completes.

Before retrying, confirm the original activity identifier, completed stages, remaining action, recipient, output and new wallet request. Never use a recovery link sent in a private message.

When a delay is not yet a failure

Uniswap says most crosschain swaps complete within a few minutes, but some can take longer because of network conditions and route-specific factors. An estimate is not a guarantee. The correct response to a delay is to identify the current stage, not to assume loss or success.

Escalate methodically when the official status is unchanged beyond the expected window, the destination proof is absent, or an explicit error appears. Preserve identifiers before refreshing, reconnecting or changing devices.

Common troubleshooting scenarios

The wallet shows only an approval

The approval may have succeeded while execution was never signed or broadcast. Check Uniswap Activity and the wallet history. Do not assume the approved tokens have already moved.

The source hash succeeded but Across shows pending

Source success and destination fulfillment are separate milestones. Confirm the order identifier and monitor official Across status. Do not revoke unrelated permissions or send another deposit while the original order remains live.

Uniswap shows completed but the wallet balance is unchanged

Switch to the destination network, verify the account and open the destination transaction. Import only the verified token contract. If the transfer went to another recipient, document the address before seeking official support.

The quote disappeared before signing

Quotes expire as prices, gas and filler conditions change. Request a new quote and review every field again. Do not approve a stale transaction through a copied link.

The destination amount is lower than expected

Compare the executed amount with the protected minimum and recorded quote. Separate source gas, quoted crosschain fee, price impact and wallet valuation changes. A fiat-value change after delivery is not necessarily execution loss.

No route is available

The network, token, direction or amount may be unsupported, or filler liquidity may be unavailable. Verify contracts and try a reasonable smaller amount. A manual bridge-plus-swap route is an alternative workflow, not a guaranteed cheaper or safer solution.

The destination chain requires gas

The delivered asset may not be the chain’s native gas token. Use a verified bridge, exchange withdrawal or supported onramp if gas is needed. Ignore strangers offering to “activate” the wallet.

A support account asks for a signature

Stop. Legitimate investigation can use public addresses and transaction hashes. Never disclose a recovery phrase or sign a transaction merely to prove wallet ownership to an unsolicited account.

Pre-swap checklist

  • Official Uniswap application opened through a trusted path.
  • Correct source account selected.
  • Source and destination networks verified independently.
  • Both token contracts verified.
  • Recipient address recorded.
  • Input, expected output and minimum output reviewed.
  • Route and Across involvement understood.
  • Total cost compared by final destination output.
  • Approval or Permit2 spender and amount reviewed.
  • Enough source gas remains.
  • A small test considered for an unfamiliar route.
  • Plan exists for destination gas and balance verification.

Post-swap verification checklist

  • Source execution hash saved.
  • Approval distinguished from the actual swap.
  • Source transaction succeeded on the correct explorer.
  • Uniswap Activity shows the correct route.
  • Across order or fulfillment status checked.
  • Destination transaction identified.
  • Recipient and token contract verified.
  • Delivered amount compared with the quote.
  • Wallet switched to the destination network.
  • Unneeded approvals reviewed after completion.
  • Hashes kept until accounting records are reconciled.

How to contact support safely

Begin from Uniswap’s official support site, not from replies on social media. Prepare public information that helps reproduce the route:

  • source and destination networks;
  • source transaction hash;
  • Across order or deposit identifier;
  • destination transaction hash, if present;
  • public sender and recipient addresses;
  • token contracts and approximate timestamp;
  • screenshot of the official status without private data.

Never provide private keys, seed words, wallet backup files, authentication codes or remote access. Support does not need them to inspect public blockchain records.

Frequently asked questions

Does a successful source transaction prove the swap completed?

No. It proves the source call succeeded. Confirm the Across fulfillment and destination token transfer separately.

Is a Uniswap crosschain swap the same as a bridge?

No. A bridge primarily changes the network of an asset, while a crosschain swap can change both network and token through a coordinated route.

Why did switching networks not move my balance?

A network switch only changes the blockchain displayed by the wallet. Moving value requires a bridge or crosschain operation.

Does Uniswap use multiple unknown bridges?

Uniswap’s current support documentation says its crosschain swaps use Across with Uniswap routing and do not introduce additional third-party bridges into that product flow. Always check current official documentation and the live route.

Who receives the Across fee?

Uniswap states that the relevant fee is paid to the relayers and liquidity providers powering Across, and that neither Across Protocol nor Uniswap receives that particular fee.

How long should a crosschain swap take?

Most complete within a few minutes according to Uniswap, but network and route conditions can extend the time. Follow the actual status rather than restarting after an arbitrary deadline.

Can every token on a supported network use crosschain swaps?

No. Network support does not guarantee every token, direction or amount has an eligible route and sufficient liquidity.

Should I repeat a pending swap?

Not until you determine whether the original is live, failed, filled or refunded. A duplicate route may also execute.

What if the token arrived but is not visible?

Verify the destination transaction, network, account and token contract. The wallet may need a refresh or a verified manual token import.

Can support reverse a completed crosschain transfer?

Blockchain transactions are generally not reversible by support. Official support can help interpret status and supported recovery paths but cannot safely request your private keys.

Final assessment

A crosschain swap is complete only when the intended destination outcome is proven—not when an approval succeeds, a source transaction confirms or a loading indicator disappears. The safest workflow preserves the quote, verifies every permission, tracks the source transaction, follows the Across fill and confirms the destination transfer against the correct token contract and recipient.

This audit trail also makes recovery safer. Instead of guessing, repeating the entire swap or trusting an impersonator, you can identify the incomplete stage and use the official retry, refund or support path connected to the original route.

Related Uniswap guides

Official Uniswap sources

Open Uniswap ↗Official website