BeraBridge Docs
  • Introduction to BeraBridge
  • What is Berachain?
  • Why Build on Bera Chain?
  • Architecture
    • Bridge Components
      • Cross-Chain Relayers
      • Validators
      • Bridge Smart Contracts
      • Cross-chain Oracles
    • Supported Chains and Interoperability
    • How BeraBridge Works
    • Security and Governance Layer
  • Proof-of-Liquidity (PoL)
    • Consensus Mechanism
    • PoL Participants
      • Liquidity Providers (LPs)
      • Validators
      • Governance Token Holders
    • Reward Vaults
      • Bridging Fees
      • $BBRG Token Bonuses
      • Special Airdrops and Early Participation Bonuses
  • Fees and Economics
    • Bridge Fees
    • Transaction Fees
    • Tokenomics
  • BeraBridge Testnet
    • Connect to Berachain
    • Faucet Token (Testnet)
    • Quest Portal
  • Support
    • Brand Assets
    • Website
    • X
    • Telegram
Powered by GitBook
On this page
  • 1. Locking Assets
  • 2. Transaction Verification
  • 3. Minting or Unlocking Assets
  • 4. Burn/Unlock Process for Reverse Transfers
Export as PDF
  1. Architecture

How BeraBridge Works

The cross-chain transfer process on BeraBridge is designed to be secure, trustless, and efficient. Here’s how it works step by step:

1. Locking Assets

When a user initiates a transfer from one chain to another (e.g., from Ethereum to BeraChain), the assets are locked in a smart contract on the source chain. For example, if the user is transferring ERC-20 tokens from Ethereum, those tokens are locked in the Ethereum smart contract.

2. Transaction Verification

The transaction is then picked up by the relayers and validators, who verify that the correct amount of assets has been locked. This involves checking that the sender has provided the correct destination address, asset type, and transfer amount.

3. Minting or Unlocking Assets

Once the transaction is verified, the destination chain’s smart contracts either:

  • Mint new tokens: If the destination chain operates on a wrapped-token model, new tokens representing the locked assets are minted on the destination chain (e.g., wrapped BeraChain tokens on Ethereum).

  • Unlock existing tokens: If the destination chain uses a locked-token model, previously locked tokens are unlocked and transferred to the user’s wallet.

4. Burn/Unlock Process for Reverse Transfers

When the user wants to send assets back to the original chain, they initiate a burn or lock transaction on the destination chain. This burns the minted tokens or locks them in a smart contract. Validators and relayers again verify the transaction, after which the original assets are unlocked on the source chain and transferred to the user’s wallet.

PreviousSupported Chains and InteroperabilityNextSecurity and Governance Layer

Last updated 7 months ago