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: how assets move between chains

crypto.news avatar crypto.news
2 min read

Berachain bridge moves assets by locking or burning tokens on Ethereum, verifying a message, then minting or releasing the equivalent on Berachain. The tokens themselves stay on their respective chains; the message authorizes the matching balance.

How the Berachain bridge moves assets

The Berachain bridge moves value through a source debit, an outbound message, verification, and a destination credit. The source transaction is your first checkpoint: it records the token debit and the message that identifies the recipient and amount.

The Berachain cross-chain bridge lets you move crypto assets between chains for use in Berachain’s DeFi ecosystem. berachainbridge.app is the Berachain bridge site for that transfer.

On an Ethereum-to-Berachain LayerZero OFT route, the source contract burns tokens before sending the message. An OFT Adapter instead locks an existing Ethereum token; the paired contract mints its representation on Berachain. LayerZero’s OFT technical reference describes this debit, message, and credit sequence. You can inspect the source transaction to see which contract received or burned your tokens.

Next, the route’s configured Decentralized Verifier Networks, or DVNs, wait for the required Ethereum block confirmations and attest to the message. After the required attestations are committed, an executor submits the verified message on Berachain. The destination contract then mints tokens or releases tokens it already holds. LayerZero’s worker services documentation explains the separate verification and delivery roles.

The confirmation wait is usually the main built-in delay, rather than the message’s travel between networks. DVN attestation and destination execution add time. A successful transfer appears as both a source debit and a destination credit to the intended address.

Say you bridge an existing Ethereum token to use it in a Berachain DeFi position. On a lock-and-mint route, compare the adapter’s Ethereum token balance with the wrapped token’s total supply on Berachain using chain explorers. For a route serving only Berachain, the locked reserve should cover that wrapped supply. If the same reserve backs several destination chains, compare it with their combined outstanding supply. Account for transfers still in flight and token decimal differences. This public reserve check tells you whether the visible backing matches the issued claims.

Route design matters: a burn-and-mint OFT depends on the issuer’s token contracts and mint permissions, while a wrapped token depends on its locked reserve. Stargate, for instance, is a LayerZero-based liquidity route, so identify its settlement model before applying a lock-and-mint reserve check. Trace the contracts and message status for your chosen route before using the received token.

What the stages mean in practice

The transfer stages tell you where to look when assessing risk, waiting for funds, or investigating a delay.

Is the Berachain bridge safe?

Safety depends on the specific route’s contracts, DVN configuration, and token backing. Inspect the paired contract addresses and mint permissions; for a wrapped token, compare its supply with the relevant locked reserve.

How long does a Berachain bridge transfer take?

A transfer takes the configured source confirmation wait plus verification and destination execution time. Watch for a confirmed source transaction, a verified message, and finally the destination credit.

What happens if a bridge transfer gets stuck?

A delayed transfer may be waiting at any of those stages. Find the source transaction first: a failed transaction creates no standard OFT transfer message. If it succeeded, use its message identifier to locate the pending stage. On a LayerZero V2 route, a verified message awaiting execution can be delivered by a permissionless executor.

Subscribe to crypto.news