Pricing Cross-Chain Swaps With Gas on Both Chains

If you swap tokens across chains only a few times a year, keep the source chain’s native gas token ready and compare the route’s quoted destination cost with its expected output. You may not need the destination chain’s gas token in advance: a relayer can pay to execute there and recover that cost through the route price.

The quote accounts for two different gas bills

Source gas is the cost of the transaction your wallet submits: typically an approval, then a deposit or swap-and-bridge transaction. On an EVM chain, the basic calculation is gas used multiplied by effective gas price; a swap that also bridges tokens uses more gas than a simple token transfer.

Destination gas pays for the transaction that delivers or swaps the asset after the cross-chain message arrives. A relayer or executor may submit that transaction from its own wallet, then include the expected cost in the route’s fee or deduct it from the amount delivered. The estimate depends on the destination gas limit, its gas price, and the asset used to reimburse the executor.

So “gas on both chains” does not necessarily mean you must hold both native tokens. Your wallet generally needs source gas for the transaction it sends. Destination gas can be prepaid through the route; a gas drop, when offered, uses part of the transferred value to leave native currency for later transactions.

Destination execution cost depends on the call

A relayer prices an execution budget, not just the act of moving a message. A simple recipient call might use roughly 100,000–300,000 EVM gas as an illustrative range; a destination swap, token approval, or contract callback can use more. The actual limit comes from simulating or estimating the specified destination action, with a margin to reduce out-of-gas failures.

The cost estimate is then converted into the route’s payment asset. In simplified terms, destination gas cost is destination gas units multiplied by destination gas price, converted at the relevant token prices, then adjusted for provider overhead and execution risk. Some chains also have separate data-posting or sequencer costs, so multiplying an EVM gas limit by a displayed gas price may not capture the whole bill.

That conversion creates a trade-off: a high gas limit helps the destination call finish but raises the quoted charge; a limit set too low can leave the message delivered without the requested swap or follow-on action completing. A route quote is therefore specific to the destination call, not a universal fee for that chain.

A two-chain example shows what to compare

Suppose you send USDC from Arbitrum to Base and want USDC on arrival. Assume, for illustration, the source transaction consumes 150,000 gas at 0.1 gwei, and the destination fill consumes 180,000 gas at 0.02 gwei. At an assumed ETH price of $2,500, those execution components are about $0.038 and $0.009 respectively, before any L2 data charge, route fee, or provider margin.

The figures are examples, not current network prices. In practice, keep enough ETH on Arbitrum for any separate approval plus the deposit transaction, then inspect the quote’s net USDC output after route fees. Compare that output with the amount you expect to receive before sending; a small transfer can be disproportionately affected by a destination execution charge that is mostly fixed per call.

Omnichain is one way to request a cross-chain token swap through a single interface. The route still has to price the source transaction, asset conversion, message delivery, and destination execution, so compare the net amount received rather than treating the displayed gas estimate as the whole cost.

Check the quote against your destination plan

Before confirming, check whether the destination action is only token delivery or also a swap or contract call, and whether you need native gas there immediately afterward. If the route offers a gas drop, compare its cost with acquiring a small amount of native currency separately; the convenience can be useful when you have no balance on the destination chain.

Quotes can age quickly when gas prices or liquidity change. Refresh the quote just before sending, check that its minimum received amount fits your tolerance, and leave a source gas reserve in case an approval is a separate transaction. For the separate mechanics of delays and recovery, see how omnichain handles pending or failed swaps; those cases depend on where execution stopped, not just on the gas estimate.

One practical warning: confirm the destination network, token, and recipient before sending, since paying destination gas does not correct a wrong destination choice.

Budget source gas in your wallet, price destination execution in the quote, and judge the route by its net delivery.