If your Berachain bridge transfer left the source chain but has not appeared on Berachain, pending usually means its cross-chain message awaits verification or execution; the funds are normally in transit. A Berachain bridge transfer links a source transaction to a destination transaction through that message. A failed source transaction or destination execution needs action rather than more waiting.
A Berachain Bridge Transfer Has Two On-Chain Stages
The first stage records the transfer on the source chain; the second credits the recipient on Berachain. Between them, the bridge waits for enough source-chain confirmations, verifies the message, and relays it for destination execution. LayerZero documentation describes verification and execution as separate steps in its cross-chain message flow. A successful source transaction therefore does not mean the Berachain transaction has happened yet.
Source-chain finality—the point at which the bridge treats a transaction as settled—can account for a long pause. This is particularly noticeable when the source is Ethereum: the bridge may wait for its required confirmations before accepting the message, even though the wallet already shows the tokens gone. The required wait depends on the route and its security settings, so a pending label alone cannot tell you whether anything is wrong.
The Explorer Trail Shows Whether to Wait or Act
The useful evidence is the source transaction hash, the message status, and any destination transaction hash. Read them in that order:
-
Source transaction: Open the hash on the origin chain’s explorer. A successful bridge deposit transaction means the source step completed and the assets entered that route. Make sure the hash is for the deposit, not merely a token approval: an approval lets a contract spend tokens but does not start the transfer. If there is no deposit hash, look in your wallet activity on the correct source chain; the bridge transfer has not started on-chain. A failed deposit also needs a new submission after you identify why it failed.
-
Message in flight: Use the bridge interface’s tracking view or the messaging explorer for its route. For a route using LayerZero, LayerZero Scan can show whether the message is still awaiting verification or has been verified but not delivered. At either stage, there may be no Berachain transaction to find. Waiting is reasonable while the source confirmations or relay step are progressing.
-
Destination execution: A delivered message should have a destination transaction to inspect. Berachain documentation identifies Berascan as the block explorer for checking Berachain transactions. Use the destination hash there to confirm whether execution succeeded, and compare the recorded recipient with your wallet address.
-
Failed execution: A message that reached Berachain but failed during execution is different from one still in flight. More source confirmations will not fix a destination error. Inspect the error and the bridge interface for a retry or resume option; use the existing transfer record rather than submitting the same deposit again.
These states describe different parts of one transfer, so a wallet’s single “pending” label may lag behind the chain. The source explorer establishes whether the deposit happened; the messaging status explains the gap; the Berachain transaction establishes whether the credit was executed.
Delivered With No Balance Usually Means the Wallet Is Hiding the Token
If Berascan shows a successful destination transaction and a token transfer to your address, the asset arrived even if your wallet displays zero. First confirm that the wallet is set to Berachain and to the recipient address shown in the transaction. Then inspect the token transfer on Berascan and add that token’s contract address to the wallet if it is missing. The token’s name alone is insufficient: bridged versions can have similar names and different contracts.
If the destination transaction succeeded but its transfer went to a different address, hiding the token is not the explanation. Compare that address with the recipient entered when you submitted the transfer and contact the route’s support with both transaction hashes.
If the Transfer Remains Unresolved, Use Its Recorded State
How do I contact the bridge’s support with my transaction hash?
Use the support channel shown in the interface where you submitted the Berachain token bridge transfer. Include the source hash, source and destination chains, token, amount, recipient address, submission time, and any message or destination hash. State the last status you can verify. Never send a seed phrase or private key; transaction hashes and public addresses are enough to investigate.
Can I cancel a transfer that is in flight?
Once the bridge deposit is confirmed on the source chain, you generally cannot cancel it from your wallet: the message is already part of the route’s process. An unconfirmed source transaction may have wallet-level replacement options, but that is different from reversing a confirmed deposit. Look up the source hash before attempting anything that could create a second transfer.
Who refunds funds if a bridge route fails permanently?
There is no universal refund rule. It depends on the route’s contracts, where the assets sit after the failed step, and whether that route provides a recovery or refund process. Give its support the transfer record and ask which recovery action applies to that specific failure. A failed destination execution may be retryable without refunding the source deposit, so establish the failure stage first.