How the Bridge Works

Architecture

The BESC Bridge uses a centralized off-chain relayer model with on-chain smart contracts for trustless verification where possible.

User on Chain A                Bridge Backend               BESC Hyperchain
      │                              │                              │
      │── deposits asset ──────────► │                              │
      │                              │── detects event ──────────► │
      │                              │   (scans chain A logs)       │
      │                              │                              │── mint()
      │                              │                              │   (wrapped token)
      │◄────────────────── confirmation ◄──────────────────────── │

Inbound Bridge (→ BESC Hyperchain)

1. You deposit the asset on the source chain:

   • ETH/BNB: send to the bridge receiver address
   • ERC-20/BEP-20 tokens: call burn() or transfer() to bridge receiver
   • XRP: send to the XRP bridge wallet address
   • SOL: send to the Solana bridge wallet

2. Bridge backend detects the deposit by scanning event logs on the source chain

3. Bridge backend signs and submits a mint() transaction on BESC Hyperchain to the wrapped token contract

4. You receive the wrapped token on BESC Hyperchain (typically within 1–3 minutes)

Outbound Bridge (BESC Hyperchain →)

1. You initiate a bridge-out via the bridge UI

2. Bridge UI calls burn() on the wrapped token contract on BESC Hyperchain

   • For native BESC bridging out: BESC is sent to the bridge receiver on BESC

3. Bridge backend detects the burn event on BESC Hyperchain

4. Bridge backend releases the native asset on the destination chain

   • ETH/BNB: sends native coins from the bridge custody wallet
   • XRP: sends XRP from the bridge XRP wallet
   • SOL: sends SOL from the bridge Solana wallet

Bridge Signer

The bridge backend uses a dedicated signer address: 0x57118D83E76dee7DB5C6b71da12b2cD625eBaB9d

This address is the authorized minter on all wrapped token contracts on BESC Hyperchain. Only this address can call mint().

Supported Scanning Intervals

The bridge backend scans all supported chains continuously:

• ETH & BSC: scans every 12 seconds (one ETH block)
• XRP: scans every 4 seconds (one XRP ledger close)
• Solana: scans every 1 second (one Solana slot)
• BESC Hyperchain: scans every 3 seconds (one block)

Security

• The bridge uses a queue system (Redis + PostgreSQL) to prevent double-processing of deposits
• All bridge transactions are recorded in a database with full audit logs
• The bridge signer key is secured server-side and never exposed client-side
• Rate limiting: 100 requests per 15 minutes per IP on the bridge API