Cross-Chain Crypto Swaps Explained: No Bridges, No Wrapped Tokens
You want ETH on Arbitrum, but you're holding $100 in USDC on Solana. Two different blockchains, two different assets, and no obvious path between them, at least not without jumping through several hoops. That's the problem cross-chain swaps solve.
What Is a Cross-Chain Swap?
A cross-chain crypto swap is an exchange between assets that live on different blockchain networks, completed in a single user-facing operation. For a hypothetical $100 swap from USDC on Solana to ETH on Arbitrum, you specify what you're sending, what you want to receive, and which network you want it on. The routing software handles everything in between.
A single user-facing operation should not be confused with a single on-chain action. A cross-chain transfer begins with a choice of assets and networks, then must validate the source-side action and deliver value on the destination side. You see one request. The underlying route has to coordinate systems that do not share a ledger. That is why the quote, destination network, and amount matter before you approve.
That's meaningfully different from a regular transaction. A regular transaction stays on one network: you send ETH from one Ethereum address to another, and the network's validators record it. Cross-chain transactions, by contrast, operate across different networks. That makes them more complex, slower, and higher risk than a same-chain transfer.
Here's why the complexity matters. Blockchains don't natively talk to each other. Ethereum has no built-in mechanism to verify what happened on Solana. Bitcoin has no idea what's in a Polygon wallet. Every method for moving value between chains must solve that fundamental isolation problem, and the solution it chooses shapes the risks it entails. The traditional solution was bridges and wrapped tokens. The newer approach can handle those steps inside the route for the user.
The Old Way: Bridges and Wrapped Tokens
A crypto bridge is a tool for transferring an asset from one blockchain network to another. For a hypothetical $100 transfer, the mechanics follow a consistent pattern: lock or burn the asset on the source chain, verify that the lock happened, then mint or release a corresponding asset on the destination chain.
The "corresponding asset" is usually a wrapped token, a representation of the original on the new chain. When you bridge BTC to Ethereum, you don't get actual Bitcoin. You get a token that represents Bitcoin, backed by the locked original. The two things are supposed to trade at a 1:1 ratio, but they're not the same. That sequence explains why a bridge transfer and a cross-chain swap can feel similar without being identical. In a bridge flow, you move an existing asset representation between networks and may then need a separate swap. A routed swap delivers the end result instead: the asset you want on the chain where you need it. The route can still rely on bridge infrastructure, but you are not asked to operate each stage yourself.
The vault distinguishes two broad types of bridges: centralized bridges controlled by a platform and decentralized bridges that run on smart contracts. Both carry risk, just different flavors of it. The risk structure breaks into three categories: smart-contract risk, bridge hacks, and operational risk.
Smart-contract risk is the attack surface of the code itself. Bridge hacks occur when the attack surface is exploited. Operational risk covers everything else: validator failures, governance decisions, and the possibility that the entity controlling a centralized bridge makes decisions you don't like.
Wrapped tokens add a layer on top of all that. The peg between a wrapped token and its underlying asset holds as long as the bridge protocol holds. If the bridge is exploited or the reserves are mismanaged, the wrapped token can lose its value. You end up holding something that was supposed to be BTC but isn't backed by anything anymore. That's the problem modern cross-chain swaps are designed to avoid.
How Modern Cross-Chain Swaps Work Instead
A route can avoid a manual bridge when the destination chain has local liquidity.
- In a liquidity-routing model, the user's source-chain asset is either deposited into a pool or received by a professional liquidity provider, while the protocol pays out an existing destination-chain asset from local liquidity. The user receives the native destination asset. It is not a wrapped copy. Settlement between the source and destination sides happens at the protocol level, not by the user.
- In an intent-based relayer model, the user signs a request describing the outcome they want: "I want X amount of asset Y on chain Z." Relayers or solvers see that request and front the destination-chain liquidity to fulfill it. A settlement layer later verifies fulfillment and reimburses the relayer. The user receives the requested native asset without ever manually bridging or holding an intermediate token.
The distinction matters when you look at the balance you expect to receive. A liquidity route can pay out an asset that already exists on the destination chain, while an intent route lets a solver supply that balance before later settlement. In both cases, the route is solving a coordination problem between chains. It is not making the chains interoperable by default. You still need to check that the selected asset and network match the wallet or application you plan to use.
For a hypothetical $100 swap from USDC on Solana to ETH on Arbitrum, you choose the assets and destination chain. The routing service can combine venues behind that request. You do not manually construct the route. Both models let you specify a source asset, a destination asset, and a destination chain, while routing software combines liquidity providers, DEXs, bridges, relayers, or solvers into a single execution flow. The result is a native destination asset, with the bridge and intermediate-token steps handled inside the route.
This is the architecture behind cross-chain aggregators. The service coordinates the intermediaries in the background, so you can choose the assets and approve a single route.
How to Do a Cross-Chain Swap in Tangem
The Tangem app aggregates and compares rates from multiple providers for cryptocurrency swaps, buying, and selling. For cross-chain swaps specifically, it routes through a set of integrated providers, with LiFi listed as the cross-chain aggregator.
The full provider list includes eight services: 1inch, OKX DEX, LiFi, Jupiter, ChangeNOW, Changelly, ChangeHero, and SimpleSwap. Tangem categorizes them by type: 1inch as a DEX aggregator; OKX DEX as a DEX; Jupiter as a Solana DEX aggregator; and ChangeNOW, Changelly, ChangeHero, and SimpleSwap as CEX swap providers.
The swap flow itself is straightforward. Open the Tangem app, select the asset you want to exchange, tap Swap, choose the asset you want to receive, and review the provider and fees. Tap Swap again, authenticate with your access code or biometric ID, and scan your Tangem Wallet card to approve the transaction. Cross-chain swaps aren’t limited to CEX providers. After you select the tokens, networks, and amount in Swap, tap the displayed provider to see which CEX or DEX options are available for that pair. Tap Status after approval to track completion on the provider's page.
Before you approve, consider more than just the quoted output. Confirm the source token, received token, and their networks. Check the provider and fee as well. A rate comparison only describes the route offered at that moment, while the slippage setting tells you how much execution may vary. These checks take a moment and directly address common user errors.
Provider fees typically range from 0.5% to 1.5%, and the app shows the slippage percentage before you confirm. Approximately 99.99% of swaps require no KYC on Tangem's side, though individual providers may apply their own requirements.
Your Tangem card's private keys are generated and stored in the secure element on the card's chip. Transaction signing happens on the card after you tap it to your phone, and the app broadcasts the signed transaction to blockchain nodes. The NFC channel between the app and card uses AES-256 encryption with a range of 0-5 cm. The secure element itself carries a Common Criteria EAL6+ certification. What this means for swaps: Tangem doesn't custody your assets during a swap or purchase. You retain self-custody throughout.
Is Cross-Chain Swapping Safe?
A routed cross-chain swap can reduce direct dependence on a single bridge by spreading execution across multiple venues, but it is not risk-free. Each route still involves its own bridges, routers, relayers, and smart contracts, so protocol risk accompanies execution.
Bridge-based routes also introduce cross-chain verification, relayer or validator, wrapped-asset, and destination-delivery risk beyond ordinary swap risks such as malicious approvals, front-running, and smart-contract failure. When a routed swap avoids wrapped tokens, it narrows the route's exposure to that particular risk category.
- Slippage and liquidity risk remain regardless. Fragmented or shallow liquidity can worsen execution, compound slippage across multiple steps, cause failed exits, and leave you with less value than quoted. Slippage protection limits how far execution can deteriorate, but it can't eliminate market movement or liquidity shortages.
Say you start with a hypothetical $25 test swap. That limits the amount exposed on the first route, but it does not change the protocol or liquidity risks. Keep that first attempt small and review the completed route.
The vault's guidance on cross-chain transfers is practical: verify the network carefully, double-check before proceeding, use trusted tools, and start with a small amount. That advice applies whether you're using a bridge or a routed swap. The stakes are real either way.
Here's what the routing model actually changes: it removes the step where you manually receive and hold a wrapped token. That's a meaningful reduction in complexity and in one specific category of risk. It's not a guarantee of safety.
FAQ
-
Shallow or fragmented liquidity can cause failed exits. After approval, use the provider's Status page to track completion, then follow the provider's route information rather than blindly sending another transaction.
-
Yes, choosing the wrong destination network is a user error risk. Before approval, match both the asset and its network to the destination you intend to use. A cross-chain route does not make a wrong selection harmless.
-
Routing software can aggregate liquidity providers, DEXs, bridges, relayers, or solvers into a single execution flow. You see a simpler route, while its underlying infrastructure can still carry protocol risk.
-
No. Starting with a small amount limits the value exposed on your first attempt, but it does not eliminate smart-contract, liquidity, or slippage risk. Verify the network and review the quoted route first.
-
Tangem's Send via Swap feature can convert a token you hold into the recipient's preferred currency and send it in a single transaction. Check the recipient's destination asset and network before you approve it.
-
Not for a routed cross-chain swap. You choose the source asset, destination asset, and destination chain, while the routing service handles the execution. That does not mean every route avoids bridge infrastructure at the protocol level.
-
Cross-chain transfers require confirmations and involve network differences, which makes them slower than same-chain transactions. The vault's cross-chain transfer guidance treats this as a structural property of the process rather than a variable to optimize around. Completion time depends on the networks and providers involved.
-
Approximately 99.99% of swaps require no KYC from Tangem. Individual providers in the swap network may apply their own requirements, and on-ramp providers handle KYC independently. Using a Tangem Wallet requires no KYC from Tangem itself.