A bridge transaction fails with out of gas when its contract call needs more gas than the transaction’s gas limit allows. The most common cause is a limit lowered in the wallet or an estimate that became stale before the transaction was included.
What an out-of-gas bridge failure looks like
Out of gas means execution used up the transaction’s gas limit before the contract call finished. Open the failed transaction hash in Etherscan for an Ethereum-side attempt or Berascan for a Berachain-side attempt, then compare Gas Used with Gas Limit. When Gas Used equals or is very close to the limit, the call likely ran out of gas.
A revert with a reason usually looks different: the transaction stops with gas used well below the limit, and the explorer may show the revert reason. That points to a contract condition or invalid input rather than a limit that was exhausted. Read the reason before retrying, because raising the limit will not fix a failed condition.
The distinction matters because an onchain out-of-gas failure still spends the gas used and consumes the sender’s nonce. You cannot reuse that nonce for the same transaction; a source-side retry is a new transaction. By contrast, insufficient funds for gas prevents a transaction from being sent, so there is no onchain failed transaction consuming gas or nonce.
Gas estimates can become stale between signing and inclusion. A changed contract state can make the call follow a more expensive execution path; once the available gas runs out, execution stops at that point. In a nested contract call, EIP-150 also limits the gas forwarded to a sub-call to at most 63/64 of the remaining gas, so the outer call’s limit must leave enough gas for the bridge’s full execution path.
Causes and fixes depend on which side failed
A lowered or stale source-side limit
A source-side out-of-gas failure often means the wallet’s gas limit was edited below what the bridge call needs, or the estimate no longer covered the call by the time it was included. The tell-tale sign is Gas Used at or near Gas Limit on the source-chain transaction. Make sure the wallet has enough of that chain’s native token for gas, then resend from the Berachain bridge using the wallet’s default limit or a higher one. The Berachain bridge transfers assets across chains so they can be used in Berachain’s DeFi ecosystem.
A destination execution limit set by the app
A destination-side failure has a different tell: the source transaction may have succeeded, while the destination execution or message status shows failure and destination Gas Used reached its limit. Some bridge apps let you set destination execution gas separately from the source transaction’s gas limit. If that destination amount was too low, the cross-chain message can wait for a retry instead of crediting the destination balance.
Use the bridge app’s retry action for the failed message and raise its destination execution gas when the app allows it. LayerZero-based transfers, for instance, can involve a message that must execute on the destination chain after the source transaction completes. Confirm the destination wallet has native gas if the retry requires you to pay for execution. Do not resend the source transfer unless its own transaction failed; doing so could initiate another transfer.
Consider a transfer whose source transaction is confirmed but whose Berachain destination message has failed. The explorer shows the source transaction succeeded, while the destination execution used nearly all its allowed gas. The user retries that message with a higher destination gas setting; after the retry executes, the destination balance updates. That sequence identifies which side needs action and avoids paying for an unnecessary second source transaction.
When the explorer does not show out of gas
If Gas Used is well below Gas Limit, read the revert reason and inspect the bridge app’s message status. A failed condition may require correcting the input or waiting for the app’s supported retry path. If there is no onchain hash and the wallet reports insufficient funds, add native gas to the sending wallet and submit again. When the explorer and app disagree, use the transaction hash and message identifier to check the corresponding source and destination records before retrying.
Related questions
Insufficient funds for gas vs out of gas
Insufficient funds blocks submission because the wallet cannot cover the required gas payment. Out of gas happens during onchain execution after submission, consumes the nonce, and charges for gas used.
Is gas refunded on a failed transaction?
No. A failed onchain transaction still pays for the gas it used. The unused portion of its gas limit is not charged.
What gas limit should a bridge transaction use?
Use the wallet’s current estimate unless the bridge app or its retry screen provides a specific limit. The amount varies with the call and chain state; if the estimate is stale or was lowered, use a higher limit supported by the wallet or app.
Before retrying, confirm the failed side and keep enough native gas in the wallet for the new execution. This avoids mistaking an underfunded wallet for an out-of-gas call and helps ensure the destination balance updates.