Introduction
Multisig coordination infrastructure for Hyperliquid assets
Welcome
Hyperliquid brings a fast, real-time, always-on environment for onchain finance.
But for a long time, Hyperliquid accounts have often been organized around a single private key. It is simple and direct, but when an account carries team funds, strategy permissions, sub-account management, or protocol operations, simple can become fragile.
Key loss or key compromise can push a risk that should be shared by an organization into a single point of failure.
Hyperliquid native Multi-Sig provides the foundation for that shared control: an account can be managed by multiple authorized users, and actions require the threshold to be met before execution.
HypeSafe builds on this native capability and provides a non-custodial multisig solution for users.
Our stack
Our goal is to make Hyperliquid Multi-Sig more than a native mechanism, but an understandable, reviewable, and executable operating system.
HypeSafe is organized around three product components:
safe-frontend
The web workspace for account setup, proposal review, approval signing, and leader execution.
safe-gateway
The keyless coordination API for templates, payloads, signature verification, approval state, and history.
safe-node
An optional self-hosted signer and policy service for automated approval or leader execution.
This documentation focuses on how those components work together to support non-custodial multisig operations on Hyperliquid.
What you'll find here
Getting Started
Create or add an account, propose an action, collect approvals, and execute.
Concepts
Authorized users, thresholds, signing tasks, execution flow, and system boundaries.
Components
Responsibilities of the frontend, gateway, and node.
What HypeSafe helps you do
- Create a Hyperliquid multisig account from a connected wallet.
- Add existing multisig accounts and keep them organized with names.
- Propose treasury and account actions such as sends, withdrawals, sub-account changes, agent approvals, and signer updates.
- Collect approvals from the required authorized users before execution.
- Keep an auditable record of proposals, signatures, rejections, and execution results.
- Run optional local nodes that enforce signer-side policy before automated approval or leader execution.
HypeSafe is not a custodian. It only coordinates the workflow, while real authorization comes from wallets controlled by authorized users or infrastructure operated by those authorized users.