LogoLogo
WebsiteEnter AppHyperliquid
  • Unit
    • About Unit
      • Team
  • How To
    • Deposit
    • Withdraw
  • Architecture
    • Overview
    • Components
    • Security
  • Developers
    • API
      • Generate Address
        • Guardian Signatures
      • Operations
        • Deposit Lifecycle
        • Withdrawal Lifecycle
      • Withdraw Queue
    • Key Addresses
      • Mainnet
        • Bitcoin
        • Solana
        • Ethereum
      • Testnet
        • Bitcoin (Testnet)
        • Ethereum (Testnet)
        • Solana (Testnet)
          • SPL Tokens
  • FAQ
    • How do I get in touch with Unit?
    • Where's my transaction?
    • How do fees on Unit work?
    • What type of Bitcoin deposit address does Unit derive?
    • How long does a deposit/withdrawal take?
    • Are there any audits planned?
    • Is my unique deposit address permanent?
    • Can I generate multiple deposit addresses for my Hyperliquid wallet?
  • Legal
    • Regulatory Compliance
    • Terms of Service
    • Privacy Policy
Powered by GitBook
On this page
  • Guardian Network
  • Agent
  • Initial Guardian Network Participants
  1. Architecture

Components

Key components of the core protocol

PreviousOverviewNextSecurity

Last updated 3 months ago

Guardian Network

The Unit Protocol is supported by a distributed leader-verifier network of independent operators known as Guardians. Each Guardian independently runs the Agent, an implementation of the protocol that:

  • Operates and uses blockchain indexers for each supported chain, verifying on-chain activity and transaction finality.

  • Participates in a 2-of-3 Multi-Party Computation (MPC) threshold signature scheme (TSS), ensuring no single Guardian can unilaterally perform operations.

  • Maintains key shares generated and stored in a distributed manner.

A leader is predetermined to coordinate proposals. The leader runs a relay server for message passing only—no key material resides there. Followers independently verify all leader messages.

Agent

Every Guardian’s Agent enforces the rules and logic needed for cross-chain flows. Four main components provide structure and clarity:

  1. Chain Services track incoming deposits, confirm finality of on-chain transactions, and build or broadcast transaction payloads.

  2. A Flow Manager oversees a multi-step state machine enforcing strict sequencing and ensuring adherence to protocol requirements.

  3. The Consensus Service implements t-of-n quorum rules (commonly 2-of-3), requiring Guardians to agree on critical operations before proceeding.

  4. The Wallet Manager handles MPC-based key operations, running within secure enclaves (e.g., AWS Nitro). It stores encrypted secret shares and coordinates threshold signatures.

Initial Guardian Network Participants

Cover

Unit

Cover

Hyperliquid

Cover

Infinite Field