Cross-Chain Swap.

A Cross-Chain Swap lets you trade a token on one network for a different token on another network in one signed flow, instead of bridging first and swapping afterward as two separate transactions. You choose the token and chain you hold and the token and chain you want, and a routing engine works out whether to swap before bridging, bridge before swapping, or split the trade across several steps behind the scenes. From where you sit, it still looks like a single quote, a single confirmation, and one or two signatures.

Swap vs Bridge: what is different

A plain bridge moves the same asset between chains — ETH on Ethereum becomes ETH (or a wrapped version) on Polygon. A Cross-Chain Swap goes further: it changes the asset itself as part of the move, so ETH on Ethereum can land as MATIC or USDC on Polygon without you ever holding an intermediate wrapped token in a separate step.

How routing finds the best path

Aggregators such as LI.FI's routing docs and Socket's documentation describe how a router compares dozens of bridge-and-DEX combinations, scoring each by net output, fees and time, then returns the best one or two routes. You still see and approve the specific path before signing.

Which tokens and chains are supported

Coverage depends on the aggregator and the liquidity available on each side. Major pairs — ETH, major stablecoins, and large-cap tokens — route reliably between Ethereum and Polygon; smaller or newer tokens may have thinner liquidity on the destination chain, which widens the price impact the quote will show you before you confirm.

Even though you see one flow, a Cross-Chain Swap is built from two legs that settle separately. Understanding both halves explains why the fee and the timing look the way they do.

The source-chain leg

On the chain you start from, your token is either swapped into a bridgeable asset or locked directly, and that transaction pays the source chain's own gas — on Ethereum, that is the gas cost documented on ethereum.org, which can be the largest single line item for a small trade.

The destination-chain leg

Once the bridge message is confirmed, the destination chain mints or releases the bridged asset and, if the route requires it, swaps it into your target token through a DEX on that side — on Polygon this final hop is cheap, since gas there runs a small fraction of Ethereum's.

A Cross-Chain Swap is priced as one quoted amount, but that number is built from fees on both legs plus the routing service's own margin. Reading the quote breakdown before you sign tells you exactly where the cost sits.

Fee component	Where it is charged	Typical size
Source gas	Paying chain (e.g. Ethereum)	Highest when Ethereum is congested
Bridge / messaging fee	Protocol moving value across chains	Small, flat or percentage-based
Destination swap + gas	Receiving chain (e.g. Polygon)	Low — Polygon gas is cheap

The sequence is the same across most aggregators, which is what makes a Cross-Chain Swap repeatable once you have done it a few times.

• Connect your self-custody wallet and pick the source chain and token you hold, and the destination chain and token you want.
• Enter the amount; the router returns a quote showing the amount you will receive, total fees and estimated time.
• Approve the source token for spending if it is an ERC-20 that has not been approved before.
• Sign the transaction that starts the route and pay the source chain's gas.
• Wait for the bridge leg to confirm, then the destination swap completes automatically and the target token lands in your wallet.

Most Ethereum-to-Polygon routes finish within a few minutes once Ethereum confirms the starting transaction, since Polygon's side of the route settles quickly. Routes through a slower bridge, or ones that queue behind an optimistic challenge window, can stretch to twenty or thirty minutes. The quote screen gives an estimate for the specific route selected, and you can track the pending transaction on Etherscan on the source side or on Polygon's own explorer once the destination leg lands. Rollups and bridges vary in how they finalize state; L2BEAT's tracking of rollup risk and finality is a useful reference if you want to understand why one route is faster than another.

A properly built Cross-Chain Swap never takes custody of your tokens — contracts route value directly between your wallet addresses on each chain, and you sign every step.

Checking the approval you grant

Before signing, check which contract is receiving a token approval and whether it is limited to the swap amount or unlimited. A limited approval means a route can only ever move the amount you intended, which keeps a future bug or exploit in that one contract from touching the rest of your balance.

Confirming the destination token

Verify the destination token's contract address against a trusted source such as Polygon's own documentation before you trust a balance that shows up after the swap. A token with the right name and the wrong contract address is a common scam pattern on new or thinly tracked pairs.

When an aggregator offers more than one route for the same pair, compare them on net amount received after every fee, not on the headline rate or the fastest estimated time alone. A route with a slightly longer settlement but a meaningfully better net output is usually the better trade for anything beyond a trivial amount. For recurring Ethereum-to-Polygon activity, it is also worth noting which bridges a route relies on, since routes built on well-audited, widely used bridges carry less protocol risk than ones built on a brand-new path with little track record.