Components
Key components of the core protocol
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:
Chain Services track incoming deposits, confirm finality of on-chain transactions, and build or broadcast transaction payloads.
A Flow Manager oversees a multi-step state machine enforcing strict sequencing and ensuring adherence to protocol requirements.
The Consensus Service implements t-of-n quorum rules (commonly 2-of-3), requiring Guardians to agree on critical operations before proceeding.
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
Unit
Hyperliquid
Infinite Field
Last updated