Getting Started

HypeSafe gives Hyperliquid accounts a safety experience closer to a centralized exchange, while keeping onchain non-custodial control.

If you do not want account security to depend on a single private key, and you want to manage funds and permissions through multiple authorized users, thresholds, operation records, and local policies, start here.

When to use HypeSafe

Consider HypeSafe when you want a Hyperliquid account to have a safety experience closer to a centralized exchange.

HypeSafe fits these situations:

• You do not want account security to depend on a single private key.
• You want multiple authorized users to manage one Hyperliquid account together.
• You want key operations such as transfers, withdrawals, Agent approvals, sub-account management, authorized user updates, or threshold updates to execute only after the threshold is met.
• You want the team to see clear proposal, approval, rejection, and execution records.
• You want automation to be constrained by local policy instead of giving a script full authority.

Recommended first flow

1. Connect your wallet and sign in.
2. Create a new multisig account, or add an existing Hyperliquid multisig address.
3. Configure authorized users and the threshold.
4. Start with a low-risk proposal so every authorized user can verify the approval flow.
5. Ask the required authorized users to review the proposal and approve from their own wallet.
6. Execute from the frontend as the selected leader after the threshold is met.
7. Add safe-node only after the manual workflow is clear.

Advanced scenario: rebalancing for trading institutions

For quantitative trading institutions, HypeSafe should not block every trading instruction.

The better pattern is to let the trading system or Agent keep executing the strategy, while HypeSafe protects the fund and permission boundaries around rebalancing.

For example, a team can put these operations behind HypeSafe:

• add capital to a strategy account;
• withdraw capital from a strategy account;
• adjust sub-account fund allocation;
• update Agent authorization;
• execute withdrawals or transfers;
• update authorized users or the threshold.

In this context, effective fund-management risk controls are usually explicit policy constraints rather than manual judgement on every operation, for example:

• destination address allowlists;
• per-transaction or periodic maximum amounts;
• allowed template types;
• allowed account scope;
• a designated leader or node execution path.

safe-node can enforce these policies locally. It signs or executes only when a task satisfies the address allowlist, maximum amount, and template constraints. Tasks outside policy should return to the manual approval flow.

What happens next

The gateway keeps the task state in sync for all participants. Each authorized user sees the same payload, the same approval progress, and the same final execution result.

Using HypeSafe explains the flow in more detail.