Arbitrum bridge
Arbitrum bridge gas funding and token arrival checks
Updated on
Arbitrum bridge ETH deposits can fund the native balance that pays for transactions on the destination network. Keep enough ETH on Ethereum to submit the deposit, then confirm the destination credit at the intended address. A token deposit requires a separate check: receiving tokens does not necessarily provide spendable gas. Completion means the correct asset has reached the correct account and network; using that asset also requires enough destination ETH for the intended transaction.
A token deposit can arrive successfully while the receiving account still lacks the native ETH needed to move it.
Native ETH arrival and a stalled token deposit
A simple native ETH deposit credits the destination account after the network processes the deposit message. Standard token deposits involve destination contract execution. That distinction matters when Ethereum shows success while the receiving balance remains unchanged. A retryable ticket allows another attempt at destination execution after an unsuccessful automatic attempt.
Recovery applies only when the transfer actually created a ticket that remains available for redemption. A pending source transaction, a missing wallet token entry, and failed destination execution require different responses. Funding a manual redemption can address insufficient execution gas. It does not fix every contract rejection, and an expired ticket requires separate investigation. Repeating the original deposit creates another transfer rather than repairing the existing one.
Source ETH before destination gas
ETH on Ethereum pays for submitting an Ethereum deposit, even when the asset moving across the bridge is a token. The source balance must cover the transaction value and its fee requirements. A token approval may also consume ETH when the existing allowance does not cover the deposit. Spending the remaining source ETH on approval can therefore leave the deposit unfunded.
Network selection is reversible before submission. Confirm the source balance, destination network, asset, and recipient before authorizing a transaction.
Arbitrum One and Arbitrum Nova both use ETH for gas, but their balances remain separate. ETH on one network cannot directly pay another network's transaction fee. Receiving native ETH through a simple deposit does not require an existing destination ETH balance. Later sending or using that ETH does require gas. For contract-based accounts, recipient handling also depends on the deposit mechanism; identical address text alone does not establish that the account can access the destination funds.
What confirms that the intended tokens arrived?
The destination execution record and the intended recipient's balance establish arrival; a successful Ethereum receipt alone does not establish destination completion. For token deposits, follow the associated message through to its successful destination execution. Ticket creation and execution are separate events, and their transaction hashes can differ. A record that shows only ticket creation leaves the token credit unresolved.
The standard token gateway pairs an Ethereum token contract with a corresponding Arbitrum token contract. Match the received asset to that destination contract, along with the recipient and amount. A ticker does not uniquely identify a token. The expected contract may differ from the source contract address. For native ETH, inspect the native account balance and deposit record instead of searching for an ERC-20 token entry. Later account activity can change the balance, so the deposit record remains useful after the funds move.
Funding choices when destination ETH is missing
A funding method solves the gas shortage only if it produces native ETH on the network where the next transaction will run. Some methods work with an empty receiving balance. Others require destination gas before they can produce more ETH. Exchange withdrawals and purchase services also depend on their supported network, asset, and account conditions.
| Funding or transfer option | Effect on destination gas | Condition that can block use |
|---|---|---|
| Native ETH bridge deposit | Credits native ETH on the destination | The source account needs ETH for the deposit and fees |
| Standard ERC-20 bridge deposit | Credits tokens without necessarily funding usable gas | The received tokens cannot directly pay ordinary ETH gas charges |
| ETH transfer within the destination network | Credits native ETH directly | The sender needs funds and gas on that same network |
| Exchange withdrawal of native ETH | Can fund the receiving account directly | The exchange must support withdrawals on the selected network |
| Direct ETH purchase through an on-ramp | Can deliver native ETH to the selected network | Network support and purchase eligibility restrict availability |
| Swap existing destination tokens for ETH | Can increase native ETH after execution | An ordinary self-funded swap requires gas and an available trading route |
| Unwrap existing wrapped ETH | Converts the supported wrapped balance into native ETH | An ordinary self-funded unwrap requires gas before execution |
Enough gas for the next transaction
The relevant gas budget comes from the transaction that you intend to submit after arrival. A simple transfer and a contract interaction can require different amounts of computation. Transactions submitted through the Arbitrum sequencer include a fee component for posting transaction data to the parent chain. Use the destination transaction estimate rather than treating the earlier Ethereum deposit fee as a reusable budget. Include any ETH that the transaction itself sends, separately from its gas requirement. Estimates change with network conditions and the requested operation.
A positive ETH balance can still be too small to fund the next transaction.
A wallet display that disagrees with chain records
A wallet can hide a completed deposit when it displays another account, another network, or an incomplete token list. Compare its selected account with the recipient in the destination record. Then confirm that it displays the same destination network. Switching networks changes the account view; it does not move funds between networks.
Adding a custom token changes the wallet display. It does not execute, accelerate, or recover a bridge transfer.
Use the destination token contract when adding a missing token entry. Entering the source contract can show an unrelated asset or no balance. If the destination record confirms the correct credit but the wallet remains stale, refresh its network connection before authorizing another transfer. If the destination record itself shows no successful execution, changing the display cannot resolve that outstanding operation.
Stopping at a usable balance
Once the expected asset appears at the intended destination address, no additional bridge transaction is necessary merely to keep it there. Retain the source transaction hash and the associated destination record. If a deposit remains unresolved, stop further deposits while identifying whether the source transaction, message delivery, or destination execution is outstanding. A pending retryable needs attention before its recorded expiry. For a completed token deposit, an insufficient gas balance calls for funding that destination account, not repeating the token transfer.
Details worth knowing about Arbitrum bridge
Do I need to sign a transaction to receive an ETH gas top-up?
An ordinary incoming ETH transfer does not require a signature from the receiving account. The sender authorizes the transfer and pays its transaction fee. A request to approve token spending is therefore a separate action, not a requirement for receiving that transfer. Initiating your own bridge deposit or manually redeeming a pending ticket does involve a transaction.
How can I reconcile a raw token balance with the amount displayed by my wallet?
Divide the raw balance by 10 raised to the destination token's number of decimal places. Wallets commonly perform that conversion automatically, while contract queries may return an integer in the token's smallest units. Do not assume every token uses the same precision. Compare the same contract and block state before treating a difference in presentation as a missing deposit.
Does a missing token price mean the bridge deposit failed?
A missing market price does not establish that a token deposit failed. Price information and token balances are separate data. The destination contract can record a balance even when a wallet cannot calculate its currency value. Assess receipt using the token contract, recipient, amount, and successful destination execution rather than the displayed portfolio value.
Can another wallet application show tokens that have already arrived?
Another compatible wallet application can display the same account's destination balance. Changing applications does not move the tokens or repeat the bridge deposit. The application must support the destination network and access the intended account. Creating a new account produces a different receiving address and will not reveal funds held at the original address.
Where does unused ETH from a retryable execution budget go?
Excess fees from a successful automatic redemption go to the fee refund address specified in the request. For manual redemption, unused donated gas funds go to the account that calls redeem. Either address can differ from the token recipient. A fee refund therefore does not, by itself, prove that the intended account received either tokens or a usable gas balance. Refunds of execution funding and refunds of a ticket's attached call value are separate mechanisms.
Can I hold tokens after they arrive without an ETH balance?
Holding a token balance does not require ongoing gas payments from its owner. ETH becomes necessary when that account submits an ordinary self-funded transaction, such as transferring the token or interacting with a contract. An empty ETH balance can prevent that activity without removing the tokens that have already arrived.