Cross-chain swaps need a gas reserve at the destination

Keep enough of the destination chain’s native token to pay for the first action after your cross-chain transfer arrives. The transfer fee on the source chain pays for submitting the transaction there; it does not automatically give your wallet gas on the destination. Before, a user could treat a bridge as a simple change of network and assume the received token was immediately usable. In practice, an asset can arrive in a wallet with no way to approve, swap, stake or transfer it until that chain’s gas token is available.

That gap matters most when the transferred asset is not itself the native gas token. A stablecoin may be the intended balance, but an EVM wallet generally needs the destination network’s native token to pay for an on-chain action. The required token and amount depend on the destination chain, the transaction and current network conditions. A route that delivers more of the desired asset can still leave less practical flexibility if it does not account for the first transaction.

Why does a cross-chain transfer need gas on both chains?

A cross-chain transfer usually needs gas on the source chain to start, and a separate balance on the destination chain to make later transactions. The first fee covers the wallet’s transaction on the network where the transfer begins. A bridge or routing service may also charge for moving or converting the asset, but that fee is distinct from gas paid by your wallet for a later destination-chain transaction.

After the transfer completes, the destination network treats your next action as a new transaction. An approval, for example, lets a contract spend a token from your wallet; a swap then trades that token. Each action may require its own gas. A route that bundles the transfer and a destination swap can arrange for execution as part of the cross-chain operation, but that depends on the service and route. It should not be assumed for a plain transfer.

When comparing a Biswap cross-chain route, look beyond the quoted output and check whether the route covers destination gas or only delivers the selected asset. The fuller Biswap route-selection guide discusses how to compare routes; the key point here is to include the first destination action in that comparison. A displayed amount of tokens is not the same as a wallet ready to use them.

How can you keep gas for the first destination transaction?

Choose a route that leaves you with, or supplies, some of the destination chain’s native gas token. There are three common ways to do that: send native tokens as part of the transfer, use a route that delivers a gas amount, or arrange a separate transfer after arrival. Each option moves the cost or effort to a different point in the process.

• Include native gas in the transfer. If the route supports it, send enough of the destination’s native token to cover the first action. This is direct, but it may require a separate asset conversion or reduce the amount of the token you wanted to receive.
• Use a destination gas option. Some services offer a gas drop or refuel feature alongside a cross-chain transfer. Check the quoted amount, fee, eligibility and supported destination. The option may be capped, unavailable on some routes or deducted from the transfer value.
• Fund the wallet after arrival. A separate transfer can work if you already have access to the destination chain and can send its native token there. It adds another step and may require gas on the sending network too.

For a first-time transfer, the clearest choice for most users is a route that explicitly shows the destination gas amount and its cost, provided the amount covers the action they plan to take. If no route offers that, plan a separate source of gas before bridging. Do not treat “gas included” as unlimited coverage: it may only fund one action, and the amount that action needs can change with network demand and transaction complexity.

What should you check before approving the route?

Check the destination network, the wallet address and the route’s final breakdown before signing. The chain name matters because similar token symbols can exist on multiple networks, while gas is paid in the native asset of the network where the transaction executes. Confirm that the destination address is yours and that the wallet can connect to the destination chain.

Then inspect what the route says you will receive. Separate the estimated token output from bridge or routing fees, any gas amount, and any destination action included in the quote. If the interface does not say whether gas is supplied, assume you will need it separately. Compare routes using the amount you can actually use after arrival, not only the headline output.

Also decide what the first action will be. A simple token transfer may need less gas than a contract interaction with several steps, and an approval may be separate from the action it enables. Keep a reserve rather than transferring every available unit of the native token into another asset. If the route fails, changes or takes longer than expected, check its status using the service’s transaction details before attempting another transfer.

How much destination gas should you keep?

Keep enough for the first planned transaction and a margin for a second attempt or follow-up action. There is no reliable universal amount: gas prices, transaction complexity and network rules vary by chain and over time. A route’s estimate is a useful starting point, not a guarantee that it will cover every later operation.

For a first cross-chain transaction, the practical rule is to preserve the destination chain’s native token before committing the rest of the balance. Check whether the route includes it, whether its estimate covers your intended action, and what you will do if it does not. Watch the final received balance, the gas amount actually delivered and the fee estimate for your first destination transaction; those signals show whether the route left the wallet ready to act.