Liquid Bridge

Liquid Bridge enables cross-chain asset transfers between the Liquid EVM and external chains. All transfers are signed by the Liquid MPC cluster — no centralized bridge operator.

How It Works

Source Chain (e.g., Ethereum)
        ↓
    Deposit to Bridge Vault (event emitted)
        ↓
    Liquid MPC Cluster (3-of-5 threshold signature)
        ↓
    Destination Chain (e.g., Liquid EVM)
        ↓
    Wrapped tokens minted to user

Withdrawals work in reverse — burn wrapped tokens, MPC signs release on the source chain.

Supported Chains

All chains supported by Liquid MPC are bridgeable:

• Bitcoin (Legacy, SegWit, Taproot)
• Ethereum + all EVM chains (Arbitrum, Optimism, Base, Polygon, BSC)
• Solana
• Cosmos ecosystem
• Polkadot
• TON
• XRPL
• And 10+ more

White-Label Tenants

Liquid Bridge supports multi-tenant white-labeling. Each tenant gets custom branding and can configure their own MPC mode:

Self-Hosted

# Set tenant config
BRIDGE_TENANT_CONFIG='{"yourdomain.com": {
  "name": "Your Exchange",
  "mpcMode": "liquid-mpc",
  "chains": ["ethereum", "bitcoin", "solana"]
}}'

Security

• All transfers require 3-of-5 MPC threshold signatures
• HSM co-signing for withdrawals above configurable thresholds
• Per-org key isolation via Liquid KMS
• Daily transfer limits enforced on-chain
• Challenge period for dispute resolution
• Slashing for malicious bridge validators

API

GET  /api/tenant?hostname=<host>    — Tenant config (branding, chains)
POST /api/v1/transfer/initiate       — Start cross-chain transfer
GET  /api/v1/transfer/:id            — Transfer status
POST /api/v1/transfer/:id/complete   — Finalize transfer

See Liquid MPC for the signing infrastructure details.