HypeSafe

Vision

Why HypeSafe exists

HypeSafe is built for a future where Hyperliquid accounts can be operated with the same flexibility as a modern team workflow, without giving up signer control.

Fast execution is only one part of asset management. Teams also need ownership structures, review processes, approval thresholds, and reliable execution records. A single wallet can move quickly, but it concentrates risk in one key and makes internal accountability difficult.

HypeSafe exists to make shared account operations practical on Hyperliquid.

Shared control without shared custody

The core principle is straightforward: coordination can be shared without making custody centralized.

HypeSafe should help people and organizations run daily account operations while keeping signing authority with the people responsible for it. The gateway can prepare payloads, verify signatures, and maintain the approval trail, but the authorization itself must come from signer-controlled wallets or signer-run nodes.

A workflow layer for Hyperliquid Multi-Sig

Hyperliquid provides the native Multi-Sig execution primitive. HypeSafe adds the product layer around that primitive:

  • account creation and account tracking;
  • proposal creation with fixed inputs and nonce context;
  • shared review before execution;
  • threshold approval collection;
  • rejection and execution history;
  • optional automation under local signer policy.

The goal is not to abstract away responsibility. It is to make the responsibility visible, reviewable, and enforceable across a group of owners.

Modular operations

Different operators need different levels of automation. Some teams only need a manual approval workspace. Others need a signer-side service that can approve low-risk actions, enforce withdrawal limits, or execute approved tasks as the leader.

HypeSafe separates those concerns. The frontend is for human review, the gateway is for coordination, and safe-node is for local policy. Each component has a clear boundary, and none of them should be able to bypass the configured multisig threshold.