Cross-chain bridges move value between blockchains, but an intent fill, a liquidity-pool transfer and a burn-and-mint protocol can deliver different token representations. Compare the asset you will actually receive, total quote cost and recovery path before signing. This comparison is based on each provider's official documentation and published features, checked in November 2026; we have not tested the tools hands-on.
Which one to pick
- Straightforward supported-chain transfers: Across, because relayers provide the quoted receiving asset.
- Several routes or a bridge-plus-swap: LI.FI, because Jumper exposes paths across providers.
- Issuer-native USDC: Circle CCTP, because transfers use Circle burn-and-mint.
- Cross-chain trade with an attached action: Squid, because its routing supports contract calls.
- Solana-to-EVM asset exchange: deBridge, because DLN orders specify the destination token.
- Pool transfers with a batching choice: Stargate, because it offers Bus and Taxi modes.
Compare cross-chain bridges by destination asset and fees
| Tool | Best for | Destination asset and transfer model | Price |
|---|---|---|---|
| Across | Moving supported tokens between chains | Relayer-delivered tokens matching the requested output | Liquidity-provider and relayer fees; possible integration charges |
| Relay | Cross-chain execution with transparent transaction steps | Solver-delivered assets through route-specific settlement | 0% bridge platform fee; $0.02 base execution charge plus destination gas; source gas paid separately |
| LI.FI | Comparing bridges and combined swap routes | Selected output tokens via aggregated bridges and exchanges | Default LI.FI transaction fee of 0.25%; bridge, swap and app fees vary |
| Circle CCTP | Transferring issuer-native USDC between supported networks | Native USDC minted after source-chain burning | No Circle fee for Standard Transfer; gas, Fast Transfer and forwarding can cost extra |
| Squid | Cross-chain swaps with optional contract execution | Requested destination tokens through auction or interoperability routes | No Squid protocol fee; gas, swaps and integrators extra |
| deBridge | Exchanging Solana and EVM assets | Specified destination tokens supplied by independent solvers | Fixed network charge plus solver expenses and gas |
| Stargate | Pool-backed transfers with flexible dispatch options | Native pool assets or Hydra OFT representations | Variable treasury and messaging fees; source gas |
| Wormhole Portal | Bridging assets across Solana-connected ecosystems | Wrapped tokens, native transfers or CCTP assets | Network gas and optional automatic-relayer fees |
The tools
Across
Intent-based transfers
Across uses an intent model: you deposit on the origin network and a relayer supplies the requested tokens to your recipient before the relayer is reimbursed. Its published coverage includes Ethereum rollups and Solana, but availability is set by the specific token pair. The fee calculation separates liquidity-provider compensation from relayer costs, covering destination gas and capital usage. Its quote also exposes amount limits and expected output. Across’s Swap API also supports cross-chain swaps and embedded destination actions.
Choose it when you have a supported pair and can verify the final receive amount.
Watch out for a listed chain does not guarantee liquidity for your exact token; integrations may charge their own fee.
Relay
Solver-executed routes
Relay provides a trading interface and APIs that return transaction steps, the receive amount and a tracking identifier. A solver handles destination execution for cross-chain orders; its protocol documentation distinguishes the different settlement mechanisms used by platform routes. Relay currently lists a zero platform percentage on token bridges, while execution has a $0.02 base charge plus applicable gas; swaps and apps can add costs. The fee breakdown differentiates execution, swap impact, platform charges and integrator fees. Refunds rely on the route and its configured return address.
Choose it when you trade through a wallet or app using Relay and need explicit execution steps.
Watch out for quotes can expire; an unset refund address can disable automatic refunds.
LI.FI
Multi-provider aggregation
LI.FI combines liquidity from bridges, decentralized exchanges and solvers rather than requiring one transfer protocol. Traders can access its routing through Jumper, which runs on LI.FI infrastructure, or through integrations inside wallets. Some routes swap tokens before and after bridging. Integrated applications can collect their own percentage fee, making the displayed net output more useful than comparing quoted bridge charges alone.
Choose it when you need to discover workable paths for a token pair or compare providers in one place.
Watch out for the chosen bridge and DEX still carry their own risks; a token appearing in search does not ensure a usable quote.
Circle CCTP
Native USDC issuance
Circle CCTP is transfer infrastructure, not a general-purpose swap exchange. For supported USDC routes, its contracts burn tokens on the sending chain and mint issuer-native USDC after Circle attestation, avoiding an additional wrapped-USDC liability. Standard USDC transfers have no Circle transfer charge, while Fast Transfer adds a route-specific fee and forwarding can cost extra. CCTP also supports native EURC and cirBTC on eligible routes and can wrap third-party assets. Circle also offers USDC Bridge, a consumer-facing interface built on CCTP.
Choose it when you specifically require native USDC on a supported destination network.
Watch out for a third-party frontend can add charges; this route does not automatically buy your destination trading token.
Squid
Cross-chain execution
Squid supplies cross-network swap and contract-call routing through its app, API and embeddable widget. Its Intents product uses a request-for-quote auction: market makers compete to fulfill the requested destination outcome, with trusted execution environments involved in settlement verification. Other Squid paths can rely on different interoperability infrastructure, so the selected execution type matters. Squid publishes no protocol charge for its own service, but source gas, underlying swap costs and integrator charges can affect the transaction.
Choose it when you want one flow that changes both chain and token, potentially with a contract action.
Watch out for Intents supports a narrower network set than Squid routing generally; Solana is listed as forthcoming for Intents.
deBridge
Non-pooled solver orders
deBridge runs the deBridge Liquidity Network, or DLN, for cross-chain orders. A user commits the source asset to a contract and independent solvers fulfill the destination side; the system does not depend on a shared bridge liquidity pool. deBridge Hooks can execute destination contract calls after an order fills. Published pricing separates a fixed charge for the network from solver execution expenses and source gas. If nobody fills an order, the protocol provides a cancellation path for reclaiming the deposit rather than treating an unfilled order as completed.
Choose it when you are exchanging assets across Solana and EVM networks with a specified receive token.
Watch out for an order can remain open without a solver fill; cancellation is a separate operation.
Stargate
Pool-backed transport
Stargate operates on LayerZero V2 and uses coordinated liquidity pools for assets such as USDC, USDT and ETH. Its wider transfer interface also handles omnichain fungible tokens. The underlying route matters: core-chain pools may deliver native assets, whereas Hydra pathways can provide an OFT representation backed by pool liquidity. Stargate offers Bus mode, which batches messages to share costs, and Taxi mode, which dispatches a single transfer. Pool credits and supported pathways constrain what can be transferred.
Choose it when you are sending an asset Stargate supports and want to choose between batching and direct dispatch.
Watch out for Bus delivery waits for dispatch; Hydra tokens are not identical to every chain’s issuer-native asset.
Wormhole Portal
Solana-connected bridge
Portal is Wormhole’s consumer bridge interface and can connect ecosystems such as Solana and Ethereum. Wormhole Wrapped Token Transfers lock assets and issue a representation on the receiving network, while configured Native Token Transfer and CCTP routes follow other asset models. Wormhole messaging uses Guardian-signed attestations; direct CCTP routes use Circle attestations. For certain wrapped-token transfers, a relayer completes the destination step; a manual route instead needs the user to redeem. Portal supports sending to a separately entered recipient wallet, but only tokens configured in its interface are available for selection.
Choose it when you need a Portal-supported cross-ecosystem transfer and have checked the resulting mint or contract.
Watch out for some transfers require redemption on the receiving chain; deploying a token with Wormhole does not list it automatically in Portal.
How to bridge USDC from Arbitrum to Base
- Identify the asset accepted by your destination market. For USDC on Base, verify the issuer-native token contract instead of relying on a symbol shared with USDC.e or a wrapped version.
- Enter the same origin, recipient and amount in Across and Relay, and inspect available alternatives through LI.FI’s Jumper. For native USDC, include a CCTP-powered option when the interface and chain pair support it.
- Read each proposed route end to end. A single-token bridge, a solver-filled exchange and an aggregator path with intermediate swaps are different transactions even if their displayed outputs look alike.
- Compare actual receiving amounts after protocol fees, source gas, destination execution, swap price impact and any app charge. Record the minimum acceptable output, not only the estimate.
- Check network availability, order limits, the recipient address, destination gas needs and the recovery or claim procedure. Reject a path that delivers a token your intended market cannot trade.
- Authorize only the intended contracts, submit the source transaction and save its hash. Track completion through the provider, then verify the destination transaction and balance before opening the trade; wallet tracking helps reconcile balances afterward.
Worked example (illustrative): Suppose you move 1,000 USDC from Arbitrum to Base and compare two hypothetical quotes. Route A delivers 998.80 native USDC with source gas equivalent to 0.35 USDC; Route B delivers 999.05 with source gas equivalent to 0.85 USDC. Their net values are 998.45 and 998.20 USDC respectively, assuming neither requires another fee or swap.
Bridge, approval and settlement risks
Use the provider’s verified domain, inspect token approvals and reject unexpected wallet signature requests; malicious lookalike contracts can divert funds before a bridge even starts. Route execution can also depend on chain finality, relayers, solvers, validators, liquidity and destination contracts, so an audit does not eliminate the possibility of loss or delay. For a substantial amount, transfer a small portion first and retain both transaction identifiers and recovery instructions.
Frequently asked questions
How much does it cost to bridge crypto?
Costs can include approval and sending gas, relayer compensation, a pool or protocol charge, swapping losses and a frontend surcharge. Estimate the value you receive net of source-chain expenses, in the same denomination for every path.
What is the difference between a bridge and a bridge aggregator?
A bridge has its own settlement contracts or messaging model; an aggregator selects among multiple providers and may insert token swaps. LI.FI is the aggregator here, while Across and Stargate operate transfer protocols.
Does Circle CCTP transfer native USDC?
Yes, on CCTP-enabled USDC domains the protocol destroys the origin balance and issues native USDC on the receiving network. A frontend must still support the chosen route and facilitate any necessary mint completion.
Can I bridge tokens between Solana and Ethereum?
Both deBridge and Portal document Solana-connected routes, and Across includes Solana in its network support. What can move depends on each token mint, the desired output and current route availability.
What happens if a cross-chain transfer gets stuck?
First determine whether the source transaction confirmed and whether the destination operation is pending, failed or awaiting a claim. Relay has route-dependent refund behavior, deBridge offers order cancellation, and certain Wormhole transfers need destination redemption.
Do I need gas on the destination chain?
Not always: a relayer or forwarding service may pay the receiving-chain transaction, normally reflected in a fee. Manual redemption and trading after receipt can still require that network’s native gas token.
Sources
Show all 21 sources
- Across — features and networks
- Across — fee calculation
- Relay — execution flow
- Relay — current fees
- Relay — refunds
- LI.FI — route aggregation
- LI.FI — app fees
- LI.FI — Jumper routes
- Circle — CCTP architecture
- Circle — published transfer fees
- Circle — supported domains
- Squid — routes and fees
- Squid — Intents model and coverage
- Squid — integrator costs
- deBridge — DLN and orders
- deBridge — fee components
- Stargate — protocol and liquidity
- Stargate — transfer modes
- Wormhole — token representations
- Portal — supported transfers
- Wormhole — claims and relayers