Check Origin-Chain Gas Before You Bridge

To avoid bridge failures from low source-chain gas, fund the wallet that submits the deposit with enough of the origin chain’s fee token to cover every required transaction. A bridge transfer begins with an on-chain action on that chain: the wallet may need to approve a token, then submit the deposit, or sign a route that combines those actions. If the wallet cannot pay the network fee, the deposit cannot be recorded. The destination-chain transfer has not started.

That distinction matters when a transfer looks stuck. A transaction rejected before broadcast has no on-chain deposit to track. A submitted transaction may remain pending or fail on the origin chain. Only after the origin-chain deposit is confirmed can a relayer fill it on the destination chain. For a route walkthrough, see AcrossBridge steps for cross-chain swaps. Treat the wallet’s fee estimate as a starting point, then check that the origin account can cover the full transaction.

What does source-chain gas pay for?

Source-chain gas pays validators or sequencers to execute the wallet’s transaction on the origin network. It is separate from the token amount being bridged. A wallet holding USDC on an EVM chain, for example, may still need that chain’s native fee token to approve the USDC and submit the deposit. The exact fee asset and transaction sequence depend on the chain and route.

Token approval is a common source of underestimation. If the token allowance is too low, the wallet may need an approval transaction before the deposit transaction. Some routes use a signature-based authorization or bundle steps differently, but a signature by itself does not guarantee the entire flow is gasless: check the route instructions to see who submits the on-chain transaction and who pays its fee.

The fee estimate combines the work the transaction is expected to use with the network’s current pricing. A congested chain can raise the fee while a transaction waits. A wallet balance that looked sufficient when the quote was requested may no longer cover the amount needed to submit it. Leave room for both approval and deposit when both are required, plus a reserve for changing network conditions.

How much fee-token balance should you keep?

Keep enough of the origin chain’s fee token for the wallet’s estimated cost of every transaction in the route, with a margin above the displayed estimate. The estimate is specific to a route and moment; it is not a fixed bridge charge. The bridge’s quoted fee and the network fee are separate costs, so a quote showing a small bridge fee does not mean the wallet needs only a small fee-token balance.

Before signing, check these items:

• Confirm the wallet is connected to the intended origin chain and holds that chain’s fee token.
• Check whether the route requires a token approval as well as the deposit.
• Review the transaction’s estimated gas limit and fee settings, and leave a reserve for price movement while it is pending.
• Confirm the wallet has enough token balance for the deposit after accounting for any token-denominated bridge fee.

Do not spend the entire fee-token balance on the deposit. The wallet may need gas later for another action on the same chain, including managing a pending transaction. Funding a small reserve before starting is usually the simpler choice than trying to recover a transfer workflow from a wallet that has no fee token left.

What should you do if the deposit does not appear?

Check the origin-chain transaction status before trying again. If the wallet rejected the transaction for insufficient funds, or the explorer shows it failed, the bridge has no confirmed deposit from that attempt. Add fee token, review the route again, and submit a fresh transaction only after the wallet shows the required balance.

If the transaction is pending, wait for the chain to resolve it before creating another deposit. Sending a second bridge transaction can create a duplicate transfer if the first one confirms later. If the wallet offers a speed-up or cancellation, that action is itself an origin-chain transaction and also needs fee token. Use the chain’s transaction details to establish whether the original transaction is still pending, confirmed, or failed.

Once the origin transaction is confirmed, use the bridge’s deposit tracker or status endpoint to distinguish a recorded deposit awaiting a fill from one that has reached a terminal state. Across’s tracker can look up a deposit by transaction hash or by deposit ID and origin chain. A confirmed deposit that is pending a relayer fill is a different problem from a failed origin transaction; topping up source gas does not make an already-recorded deposit fill faster.

Does low source gas affect the destination fill?

Low source-chain gas prevents or delays the wallet’s deposit transaction; it does not directly pay for the relayer’s destination-chain transaction. In a relayer-based bridge, the relayer uses its own destination-chain funds to deliver tokens after it observes the origin deposit. Its destination gas, liquidity, and route conditions govern that fill. Once the source deposit is confirmed, inspect its status rather than repeatedly resubmitting it.

The practical rule is straightforward: verify the fee token, count every origin-chain step, and preserve a reserve before signing. Then track the confirmed deposit by its transaction record. This separates a wallet funding problem from a bridge-fill delay and avoids creating another transfer while the first one is unresolved.