defi

Converting Network-Native Coins for Transaction Fees

You convert a bridged asset into a network-native coin by swapping it through a DEX aggregator that ends in the destination chain’s native gas asset. On Arbitrum One, that means ETH. You can bridge USDC to Arbitrum One, see the balance appear, and still be unable to move it, because every transaction costs ETH, and your fresh wallet has zero. The bridge got the value onto the chain. The conversion is what turns it into something the fee market accepts.

Most bridge walkthroughs stop at the “received” screen. The skipped step is exactly this one: an arrived ERC-20 balance is not automatically usable for network fees. A network-native coin is the only thing a node accepts as gas, and unless the bridged asset itself is that native coin, a conversion step has to happen.

Native coin, not wrapped token

The distinction that matters is between a network-native coin and its wrapped representation. Arbitrum One’s native gas coin is ETH. WETH is an ERC-20 wrapper for ETH, used in DEX pools and lending protocols. A swap quote that returns WETH has not solved the gas problem, because the transaction that unwraps WETH to ETH costs gas, and gas is paid in ETH. The route needs to end in native ETH, or include the unwrap in the same settlement transaction.

ParaSwap handles this by routing through sources such as Uniswap Protocol and0x Protocol, then treating native ETH asthe settlement asset rather than WETH. The step that connects the bridge receipt to a usable gas balance is routing a swap through an aggregator. The aggregator contract pulls your bridged token, buys WETH along the route, unwraps it, and sends ETH back to you, all in one transaction.

In order, the mechanics are:

  1. Your wallet authorizes the aggregator to spend the bridged token—via a permit signature ifthe token supports one, otherwise via a prior approval transaction.
  2. The aggregator splits the order across the price sources it selected—Uniswap Protocol pools,0x Protocol liquidity, others—to move from USDC to WETH as efficiently as possible.
  3. The final hop unwraps WETH to ETH.
  4. The contract returns net ETH to your address; leftover dust stays in the pools or as fees.

Notice what is notin that list: a second transaction. The conversion is folded into one settlement flow, so the output arrives as ETH. But the gas for that single transaction still comes from your existing ETH balance. If your wallet has exactly zero ETH, it cannot even call the aggregator, regardless of whether the route would end with ETH. The conversion consumes a gas seed; it does not create one.

The edge a builder needs to design for

The aggregation layer exposes clean primitives: quote, amountOutMin, route, call data. It assumes you already have funds, an approval path, and enough native coin to pay for the transaction. It does not expose a way to bootstrap a zero-gas wallet. Some brides include a small gas drop, or use an intent relayer that pays gas from the settled output; those address the gas-seed problem externally. If you build the same flow yourself, the practical order is: bridge, gas seed, approve, swap. Any order that puts swap before seed gets stuck at zero.

The one-block window after bridging is worth designing for. On Arbitrum One, a user who bridged exactly the amount they plan to swap still cannot do the swap until ETH has arrived from some source. That source can be a small exchange withdrawal, a bridge-side gas service, or a keeper; whatever it is, it has to arrive before the conversion. A bridge flow that handles this well quotes the destination asset plus a small native gas reserve as one output, so the user leaves with both liquidity and fee-paying ability.

There is also a liquidity condition. The aggregator route assumes a liquid path exists from the bridged asset to the network-native coin. On an app chain with a thin pool that path may not exist. In that case the bridge’s native gas reserve or a dedicated faucet is the only way in; no aggregator can manufacture a market that is not there.

What you end up with is simple: a native ETH balance that can pay the next Uniswap Protocol interaction, the next bridge transfer, the next protocol call. That is the real completion condition for a cross-chain transfer. The token balance is the asset;the native coin balance is the ability to act.