Berachain bridge moves assets across chains by taking a source chain, destination chain, token, amount, recipient and native fee. A Berachain bridge transfer first gives your app a source transaction hash and a message ID; the destination transaction arrives later. Delivery is asynchronous, so your UI should keep the transfer pending after the source transaction confirms.
Berachain bridge transfers produce two transaction records
Say a user sends an illustrative 100 USDC from Ethereum to Berachain through a supported LayerZero route. Your app approves the source USDC contract for the route’s spender, quotes the native fee immediately before sending, then submits the transfer. A fee below the required quote makes the send revert on Ethereum. Berachain mainnet’s EVM chain ID is 80094; LayerZero’s endpoint ID is a separate value used by its messaging contracts.
- Inputs: srcChain, dstChain, token, amount, recipient and nativeFee.
- First outputs: srcTxHash and a LayerZero GUID, the unique ID for this message.
- Later output: dstTxHash, once execution credits the recipient on Berachain.
The source transaction starts the message; verification and destination execution follow. Get the transaction hash from the Ethereum receipt and the GUID from the message event. Store both against one transfer record. LayerZero identifies packets by GUID and separates sending, verification and receipt into distinct stages in its protocol description.
Token mapping matters just as much as message tracking. Ethereum USDC has a source contract address; the asset credited on Berachain has its own destination contract address. Keep a mapping keyed by chain and token route, and use the Berachain address when reading the recipient’s balance or adding the asset to a wallet. Reusing Ethereum’s address would query the wrong contract. HONEY is a separate token, so a USDC transfer should remain labelled USDC throughout the UI. Confirm supported token addresses against the route and Berachain’s token list.
Before the send, the user holds USDC on Ethereum and the Berachain balance has not changed. After Ethereum confirms, the source transaction and GUID exist, while the Berachain credit is still pending. Show delivered only after destination execution succeeds and record its transaction hash. If the source send reverts, show failed with no cross-chain message to track.
A failed destination execution needs a different state: the verified message remains available for retry. Poll by GUID, retain the original source transaction and avoid prompting a second send. The practical rule is simple: the source receipt proves submission; the destination receipt proves delivery. Keeping those events separate lets the UI report pending, delivered and failed transfers accurately.
Related questions
How to track a Berachain bridge transaction
Track the transfer by its GUID in LayerZero Scan, then attach the destination transaction to the same record when execution succeeds. Its message data can be retrieved by GUID or transaction hash and includes status and transaction details.
Berachain bridge on testnet
Use testnet chain settings, deployed route contracts and test tokens together. Keep testnet token mappings and transfer records separate from mainnet, even when the UI uses the same pending and delivered states.
Questions to answer next
Is there an API for Berachain bridge quotes?
Quote through the specific route your integration uses, such as its contract quote method or provider API. Pass the same transfer parameters to the quote and send calls, then refresh the native fee just before submission.
How do I add Berachain to a dApp's wallet connect list?
Add Berachain mainnet as chain ID 80094 in your wallet configuration. Keep that EVM chain ID separate from LayerZero’s destination endpoint ID.
How do I refund a failed bridge message?
First distinguish a reverted source send from failed destination execution. A reverted send needs no bridge refund; a destination failure calls for retry or the route’s documented recovery process. Do not promise an automatic refund while the message can still execute.