Community Docs
  • 🏠Home
  • Getting Started
  • Introduction
    • What is Hyperliquid?
    • Hyperliquid Labs
    • Roadmap
      • 2025-26-03_Incident
  • Architecture
    • Overview
    • HyperBFT
      • API Servers
    • HyperCore
      • Dex
        • Clearinghouse
          • Margin Management
          • Liquidations
          • Funding
          • Fees
        • Order Book
        • Oracle
      • Vault
      • HIPs
        • Spot Deployments (HIP-1/HIP-2)
      • Bridge
    • HyperEVM
    • Hyperliquid.
      • Unit
  • Guide
    • User Guide
      • Onboarding
      • Spot Deployments
      • Airdrop
    • Builder Guide
      • HyperCore
        • Trading Bot
        • Builder Codes
          • Install Template
          • Update
        • Endpoints
          • Info
            • Spot
            • Perpetuals
          • Exchange
      • HyperEVM
        • EVM Basics
          • dApp Setup
        • Specificities
      • Node Operators
      • Historical Data
  • Ecosystem
    • The Hyper Liquidated
      • Community Map
    • Projects
      • Tools
      • HyperEVM
        • Felix
      • HyperCore
      • MemeCoin
Powered by GitBook
On this page
  • Key Features 🛡️
  • Additional Features
  1. Architecture
  2. HyperCore

Bridge

The Hyperliquid Bridge connects the Hyperliquid L1 and the EVM Arbitrum chain, providing a secure and efficient mechanism for transferring assets between these two ecosystems.


Key Features 🛡️

  • Validator-Secured Bridge:

    • The bridge is secured by the same validator set as the Hyperliquid L1.

    • Deposits and withdrawals require signatures from more than 2/3 of the staking power to ensure security.

  • Deposit Process:

    • Deposits to the bridge are signed by validators on the L1.

    • Once validated by 2/3 of the staking power, the deposit is credited on the bridge.

  • Withdrawal Process:

    1. Escrow on the L1: Withdrawals are immediately locked on the L1 upon request.

    2. Validator Signatures: Validators sign the withdrawal as separate L1 transactions.

    3. EVM Bridge Interaction: When 2/3 of the staking power signs the withdrawal, an EVM transaction can be sent to the bridge to complete the process.

  • Dispute Protection:

    • After a withdrawal is requested, there is a dispute period to detect and block malicious withdrawals that do not match the L1 records.

    • If needed, the bridge can be locked using cold wallet signatures from 2/3 of stake-weighted validators.

  • Finalization:

    • After the dispute period, finalization transactions distribute the USDC to the appropriate destination addresses.


Additional Features

  • Validator Management on the Bridge: The bridge maintains an active validator set with their corresponding stake, ensuring synchronization with the Hyperliquid L1.

  • No Arbitrum ETH Requirement for Withdrawals:

    • Users do not need to provide Arbitrum ETH for gas fees.

    • Instead, a withdrawal fee of 1 USDC is paid on the L1 to cover validator costs.

  • Audited for Security: The bridge logic, in conjunction with L1 staking, has been audited by Zellic.

PreviousSpot Deployments (HIP-1/HIP-2)NextHyperEVM

Last updated 5 months ago

For more details, see the and the audit reports.

Hyperliquid GitHub repository