Phantom Cross-Chain Swapper combines swaps and bridge transfers so a user can exchange an asset on one blockchain for an asset on another. A single confirmation can hide several operations: a source-chain swap, bridge deposit, relay or validator confirmation, destination release and sometimes another swap. Understanding that route is essential when comparing costs or diagnosing a transfer that appears stuck.
Last reviewed: October 2, 2026. Phantom can change supported networks, bridge providers, fees, Refuel availability, quote presentation and recovery procedures. Review the live route and current official Help Center before signing. This independent guide is educational and is not financial, tax or investment advice.
What is a Phantom cross-chain swap?
A same-chain swap exchanges tokens on one blockchain. A cross-chain swap also moves value between independent networks. Because one chain cannot directly update another, a bridge provider coordinates the source deposit and destination delivery.
The asset received may differ from the asset sent, and the route may contain one or more swaps around the bridge step. Phantom presents the workflow in one interface, but the underlying contracts and providers remain important.
Cross-chain swap, bridge and ordinary swap
| Operation | Source and destination | Typical result |
|---|---|---|
| Same-chain swap | One network | Token A becomes token B on the same chain |
| Bridge transfer | Two networks | Value moves to a corresponding asset on another chain |
| Cross-chain swap | Two networks and possibly different tokens | Swap, bridge and destination conversion are combined |
A route from SOL on Solana to ETH on Base, for example, can require an intermediate asset and provider even though the interface displays one requested outcome.
How Phantom builds a route
Phantom requests quotes from supported bridge infrastructure and compares price, fees, liquidity and expected speed. Its Help Center currently lists providers including LI.FI, which can integrate tools such as Mayan, as well as Relay, deBridge and Garden.
The cheapest displayed provider may be selected automatically, while swap settings can allow manual provider selection. Provider availability depends on the exact tokens, networks, amount and current liquidity.
The four possible stages
- Source conversion: the input token may be swapped or wrapped into an asset the bridge supports.
- Bridge deposit: the bridge locks or burns the source-side asset according to its design.
- Cross-chain confirmation: validators, relayers or messaging infrastructure verify the source event.
- Destination delivery: assets are released or minted, followed by a final swap if the requested token differs.
Some routes omit one of the conversion stages. Others create multiple onchain transactions. Read the route rather than assuming every quote uses identical infrastructure.
Why cross-chain swaps take longer
A same-chain swap usually waits for one network. A cross-chain route can wait for source finality, provider validation, relayer action, destination finality and an additional swap. Congestion or insufficient destination liquidity can slow any stage.
An estimated arrival time is not a deadline or guarantee. The transaction may be progressing even when the destination balance has not changed yet.
Supported networks are route-dependent
Phantom supports multiple ecosystems, but owning an address on a network does not guarantee a cross-chain route for every token pair. Provider coverage, liquidity, token contracts and regional product availability can change.
Always choose networks inside the current Phantom quote interface. Do not send tokens manually to a visually similar address on an unsupported chain merely because Phantom displays both networks elsewhere.
Bridge providers: what changes between routes
| Variable | Why it differs | What to check |
|---|---|---|
| Expected output | Liquidity and exchange rates vary | Minimum or guaranteed received amount |
| Estimated time | Different messaging and confirmation designs | Provider ETA and current network conditions |
| Bridge fee | Provider pricing and route structure | Provider details in swap settings |
| Security model | Contracts, validators and relayers differ | Provider documentation and incident history |
| Refund behavior | Failure handling is protocol-specific | Whether refund or manual claim is possible |
| Destination asset | Native, canonical or wrapped delivery may differ | Network and token contract address |
Automatic versus manual provider selection
Automatic selection reduces work and can choose a competitive live quote. Manual selection lets an experienced user compare route, provider, duration and fees. Neither option eliminates smart-contract or liquidity risk.
Do not choose only by the largest estimated output. A small difference may reflect a slower route, unfamiliar wrapped asset, greater failure risk or different refund process.
Best Return versus Fastest
Where Phantom offers route priorities, Best Return emphasizes expected destination value while Fastest emphasizes estimated completion time. The fastest route can cost more, and the best quoted return can take longer.
Both values are estimates derived from current conditions. Check the final confirmation because a route can be recalculated after price or liquidity changes.
Cross-chain swap fees
Phantom identifies up to four broad cost components:
| Cost | What it pays for | How it appears |
|---|---|---|
| Source network fee | Approval, swap or bridge transaction on the origin chain | Paid in the source network’s gas asset or supported gasless mechanism |
| Bridge fee | Provider infrastructure, liquidity and cross-chain delivery | Can be included with price impact in the main view |
| Destination network fee | Release, mint or final swap on the destination | May be incorporated into the quote |
| Price impact | Difference caused by available liquidity and order size | Reflected in expected output |
Other product or provider fees may apply. Use the Provider area in swap settings to inspect the current breakdown before approval.
Why “no separate fee” can still have a cost
A route can advertise no explicit bridge charge but deliver less because of swap spreads, price impact, relayer economics or destination gas. Compare the complete input with the final minimum received—not one fee label in isolation.
For large amounts, compare several quote sizes. Liquidity impact is not always linear.
Price impact and slippage
Price impact reflects how the trade size interacts with available liquidity. Slippage tolerance defines how much execution deterioration the user accepts before a swap stage should fail or re-quote.
Very high tolerance may allow a poor fill or expose the trade to adverse execution. Very low tolerance can cause failure after a source transaction has already consumed gas. Use the live default as a reference, then change it only when the reason is understood.
Minimum received matters more than the headline quote
The headline output is an estimate. A minimum or guaranteed amount, when provided, describes the lower execution boundary under the route’s terms. Check which destination token and network that amount refers to.
If no clear protection is shown, understand how the provider handles price movement before signing.
What is Refuel?
Refuel is designed to deliver a small portion of value as the destination network’s native gas token. It helps prevent the user from arriving with a token balance but no ETH, SOL or other required asset to make the next transaction.
Availability and amount depend on the route. Refuel is not free money: its value and related cost are part of the overall quote. Verify how much destination gas will arrive and whether it is enough for the intended next action.
Destination gas planning
Without Refuel, a user may need to acquire the destination gas asset separately. Do not bridge the entire source balance if the source still needs gas for approval or the bridge deposit.
Plan for:
- the approval transaction where required;
- the source swap and deposit;
- possible recovery or refund actions;
- destination token approval and next transaction;
- normal fee volatility during congestion.
Native, canonical and wrapped tokens
A bridge may lock a token on the source chain and mint a representation on the destination. That representation can have a different contract address and may not be the canonical form most dapps expect.
Phantom may perform a final swap into the requested asset, but users should still verify the received token contract. A ticker such as USDC or ETH is not a unique identity across every network.
How to make a cross-chain swap safely
- Open the verified Phantom application or extension.
- Select the account that holds the source asset.
- Open Swap and choose the source token and network.
- Select the destination network and token.
- Enter the amount while preserving required source gas.
- Review provider, route, expected time and minimum output.
- Open fee and provider details instead of relying only on the summary.
- Check Refuel or destination gas availability.
- Verify every approval, signature and transaction request.
- Submit once and monitor Activity until final completion.
Use a test transfer
For a material amount or unfamiliar route, a small test can verify the destination account, token representation and provider workflow. It costs additional network fees, so compare the security value with the cost.
A successful test does not guarantee a later large quote will use the same route or price. Review the main transaction independently.
Token approvals before bridging
An EVM source token may require an approval before the bridge or swap contract can transfer it. Approval is a separate onchain permission and can remain after the cross-chain swap completes.
Verify the spender, token and allowance. Prefer a limited amount when supported and review unused approvals later. Disconnecting Phantom from a dapp does not revoke an onchain allowance.
How to track a Phantom bridge transaction
- Open Phantom Activity and select the cross-chain swap.
- Identify the source transaction signature or hash.
- Confirm its status on the source-chain explorer.
- Open the provider tracker when Phantom supplies a link.
- Check whether the route is waiting for confirmation, relay or destination execution.
- Identify the destination transaction hash once created.
- Confirm the received token contract and balance on the destination explorer.
A source transaction marked successful proves only that its source-chain instruction executed. It does not by itself prove final destination delivery.
Cross-chain status meanings
| Status | Likely meaning | Recommended action |
|---|---|---|
| Awaiting signature | The wallet has not authorized the required step | Inspect pending wallet prompts; do not approve duplicates |
| Pending source | The source transaction is not final | Check source explorer and current gas conditions |
| Bridging / in progress | The provider is validating or relaying | Track the provider route and wait |
| Destination pending | A destination action has not finalized | Check destination explorer and provider status |
| Completed | The route reports successful delivery | Verify correct token and amount in the destination account |
| Failed | A route stage did not complete | Determine whether refund or manual claim is required |
| Refunded | Value returned according to provider rules | Verify asset, network and returned amount |
Why a swap can appear stuck
- the source network has not confirmed the transaction;
- the provider requires additional finality;
- a relayer or validator set is delayed;
- destination gas prices increased;
- destination liquidity changed;
- a final swap failed while the bridge delivery succeeded;
- the wallet interface has not refreshed the status;
- the destination token is hidden or unfamiliar;
- the route requires a claim action.
Do not submit the same swap again immediately
If the source deposit succeeded, a second submission can create a second bridge transfer rather than accelerate the first. First find the source hash and provider status.
Refreshing Phantom, switching network view or reopening Activity is safer than signing another transfer without understanding the current one.
Source transaction failed
If the source explorer marks the transaction failed, the bridge may not have received the deposit. Network gas can still be spent. Check whether a preceding token approval succeeded even though the main bridge action failed.
Request a fresh quote before retrying. Old route data, nonce or slippage conditions may no longer be valid.
Source succeeded but destination is missing
This is the classic bridge troubleshooting case. Record the source hash, provider, source and destination networks, tokens, amount, account address and submission time. Use the provider tracker to locate the cross-chain message.
Do not share a recovery phrase or private key with support. Public transaction identifiers contain enough information to investigate normal routing.
Final destination swap failed
Sometimes the bridge delivers an intermediate asset but a destination conversion fails. The wallet may therefore hold a wrapped token or stablecoin rather than the requested output.
Verify the delivered contract on the explorer and consult the exact provider recovery path. Do not interact with an unknown token based only on its symbol.
Refunds and manual claims
Refund behavior is provider-specific. Some routes automatically return value to the source address; others may require a claim on the source or destination network. A claim can require gas and a verified provider interface.
Use links from Phantom Activity, the provider’s official domain or verified documentation. Fake “bridge recovery” pages frequently request unlimited approvals or recovery words.
When to contact Phantom or the provider
Contact official support when the provider tracker shows an unexplained failure, an estimated window has passed materially, a refund or claim is unclear, or Phantom and explorer statuses disagree.
Provide:
- source transaction hash;
- destination transaction hash if one exists;
- source and destination networks;
- public wallet address;
- token contract addresses and amount;
- provider and route identifier;
- timestamps and non-sensitive screenshots.
Bridge smart-contract risk
Bridges hold or coordinate assets across systems and have historically attracted attacks. A provider can suffer contract bugs, compromised validators, oracle failures, liquidity shortages or governance problems.
Phantom integration and routing do not guarantee that every underlying provider can never fail. Limit exposure, avoid leaving unnecessary approvals and consider whether the route’s convenience justifies its additional trust assumptions.
Relayer and liquidity risk
A route may depend on relayers to deliver messages and liquidity providers to supply destination assets. Delays or unavailable liquidity can affect speed and output even when source contracts function correctly.
For urgent transfers, compare route depth and provider status rather than choosing only by a small price advantage.
Destination address risk
Phantom normally sends to the corresponding address of the selected account, but network account models differ. Verify which destination address will receive the asset, particularly when using imported, hardware or special-purpose accounts.
A transfer to the wrong supported network may be difficult to recover; a transfer to an incompatible destination can be permanently lost.
Account and network checks
- The source account actually controls the displayed assets.
- The destination account is available after the network changes.
- The selected token contracts are genuine.
- The route does not produce an unwanted wrapped representation.
- Enough source gas remains.
- Enough destination gas or Refuel will be available.
- Hardware-wallet prompts match the Phantom summary.
Tax and accounting records
A cross-chain swap can contain taxable disposals, acquisitions, fees and transfers depending on jurisdiction. The source and destination transactions alone may not clearly show the complete economic route.
Save the Phantom quote or receipt, provider identifier, both transaction hashes, input amount, final output and fee breakdown. Consult a qualified tax professional for local treatment.
Common Phantom bridge mistakes
- Assuming one interface means one blockchain transaction.
- Bridging the complete native balance and leaving no source gas.
- Comparing quotes without opening provider details.
- Confusing estimated output with minimum received.
- Ignoring the destination token contract.
- Submitting a duplicate while the first route is pending.
- Looking only at the source explorer.
- Believing a successful deposit guarantees completed delivery.
- Sending an unsupported token manually to another network.
- Approving a fake manual-claim website.
- Sharing recovery words with supposed bridge support.
- Forgetting persistent token approvals after completion.
Pre-swap checklist
- Official Phantom application verified.
- Correct source account, chain and token selected.
- Correct destination chain, address and token selected.
- Provider and complete route reviewed.
- Expected and minimum received amounts understood.
- Source, bridge, destination and price-impact costs checked.
- Source gas reserved.
- Destination gas or Refuel planned.
- Slippage and expected duration accepted.
- A small test considered for a material or unfamiliar route.
- Transaction will be monitored until destination completion.
Frequently asked questions
What is Phantom Cross-Chain Swapper?
It is Phantom’s in-wallet interface for exchanging assets across different blockchains through supported bridge providers and swap routes.
Which bridge providers does Phantom use?
Current Phantom documentation lists providers including LI.FI, Relay, deBridge and Garden. Exact availability depends on the route and can change.
How does Phantom choose a provider?
Phantom compares quotes using price, fees, speed and liquidity considerations and can automatically choose a route. Users can inspect and, where available, select a provider in swap settings.
Why is my Phantom cross-chain swap pending?
It may be waiting for source confirmation, bridge validation, relayer execution, destination finality or a final swap. Check Activity, explorers and the provider tracker.
Can I cancel a cross-chain swap?
Usually not after the source bridge transaction is confirmed. Cancellation and refund behavior depend on the provider and current route state.
What fees does a Phantom bridge charge?
A route can include source network, bridge, destination network and liquidity-related price-impact costs, plus any current product fees shown in the quote.
What is Phantom Refuel?
Refuel can deliver part of the transferred value as the destination chain’s native gas token so the user can transact after arrival.
Why did I receive a wrapped token?
The provider may use a wrapped representation for cross-chain delivery, or a final destination swap may not have completed. Verify the contract and route status.
Should I repeat a stuck bridge transaction?
Not until the first transaction’s source and provider status are known. Repeating a successful deposit can send the amount twice.
Does Phantom control the bridge provider?
Phantom provides routing and interface integration, while cross-chain execution relies on third-party provider infrastructure and contracts. Review the selected route before signing.
Final perspective
Phantom makes a multi-stage bridge route look like one wallet action, but the underlying process still crosses independent networks and providers. The most important details are the route, minimum output, complete fees, destination token and recovery path.
After submission, treat Activity as the starting point and confirm source, provider and destination states separately. Most troubleshooting mistakes come from looking at only one stage or submitting another transfer before the first route has finished.
Official sources
- Phantom — Understanding cross-chain swaps
- Phantom — What is a crypto bridge?
- Phantom — Bridging tokens across chains
- Phantom official blog