Start typing to search this publication.
crypto.news logo crypto.news
Open menu
crypto.news logo

Subscribe to crypto.news

Get new posts delivered straight to your inbox.

Berachain bridge Transfer Pending for Hours: Two Stalling Points

crypto.news avatar crypto.news
2 min read

Trace a Berachain bridge transfer pending for hours by checking its source hash, then its message status: usually the source transaction is unconfirmed or a verified message has failed to execute on Berachain. The Berachain bridge moves assets between Berachain and another chain for DeFi use; a Berachain asset bridge transfer has separate source and destination stages. Either stage can stall independently.

  • Source transaction: confirmation on the sending chain.

  • LayerZero message: verification after the source event.

  • Destination execution: asset credit on Berachain for an inbound transfer.

A confirmed source transaction starts the cross-chain process, but the message still needs verification and destination execution. That is why the source hash comes first.

Start on the source explorer: Etherscan for Ethereum, Arbiscan for Arbitrum, or Berascan for Berachain. A pending hash or earlier stuck nonce points to low gas or a nonce gap. The oldest pending transaction blocks every later transaction with a higher nonce from that wallet. Speed up the oldest transaction with a higher gas bid using the same nonce; replace it with that nonce to cancel it if appropriate. MetaMask Support documents this replacement method. Verify the resulting hash before proceeding.

Do not submit a fresh transfer just because the first has waited for hours. Say an earlier nonce clears after you resend: the original bridge transaction and the new one can both confirm, and both messages may deliver. You could move twice the intended amount. First establish whether the original hash confirmed, failed, was replaced, or was dropped, then inspect its message. A same-nonce replacement competes with the original transaction; a fresh bridge send uses another nonce. Once the original confirms, work on its message instead of sending assets again.

With source confirmation, LayerZero Scan shows a status for each message associated with that source hash and a destination hash when present. Inflight calls for waiting while the message progresses; Delivered means destination delivery completed. Failed or Payload Stored after verification points to execution trouble on Berachain for an inbound transfer. Retry the existing message through LayerZero Scan when that action is available, after checking the failure reason. LayerZero V2 permits execution retries, but a persistent error must be fixed first. The funds remain recoverable through the message once execution succeeds.

If neither pattern matches, confirm the hash represents the intended route’s bridge send rather than an approval. When Scan says Delivered but the asset is absent, compare its destination hash on Berascan with the recipient and token contract. Give the team both hashes and receipts to investigate the discrepancy.

Log the source hash, route, amount, and approver for each transfer. Let one owner authorise any replacement, execution retry, or fresh send, recording the original’s status first. That gate prevents a late delivery from becoming a duplicate payout.

Subscribe to crypto.news