Cross-Chain Bridges

The Interoperability pallet (runtime index 27) connects BelizeChain to external networks — Ethereum and the Polkadot ecosystem — with post-quantum signature verification (ML-DSA-87, FIPS 204) protecting bridge messages.

Supported Bridge Types

Which assets are actually enabled is controlled by the on-chain asset registry — each asset has an active flag set through governance.

Wrapped Assets

Bridged assets are represented as wrapped tokens with a w prefix:

Asset Registry

Each registered asset is configured with:

• Local representation — the PSP22 contract on BelizeChain
• Bridge type — Ethereum or XCM
• Minimum / maximum deposit limits
• Bridge fee in basis points
• Daily volume limit
• Status flags — active and verified

pub struct AssetConfig {
    pub local_id: AccountId,       // PSP22 contract on BelizeChain
    pub symbol: String,            // e.g. "wETH"
    pub decimals: u8,
    pub bridge_type: BridgeType,   // Ethereum | PolkadotXCM
    pub external_address: Vec<u8>, // ERC-20 address or XCM location
    pub minimum_deposit: u128,
    pub maximum_deposit: u128,
    pub bridge_fee_bps: u128,      // 10 = 0.1%
    pub daily_volume_limit: u128,
    pub active: bool,
    pub verified: bool,
}

Liquidity Integration

Bridged assets can be paired against DALLA or bBZD on the BelizeX DEX, either through a standard liquidity-provider flow or atomically as part of a bridge operation. See BelizeX AMM for the AMM mechanics.

Security Model

• Verification — bridge messages carry ML-DSA-87 (NIST FIPS 204) post-quantum signatures
• Rate limiting — per-asset daily volume limits constrain exposure
• Verification gating — assets must be marked verified before activation
• Relayer monitoring — relayer health and message throughput are monitored as part of network operations

Related

• Interoperability pallet — runtime index 27
• Bridges overview page
• BelizeX DEX