Using HypeSafe
Basic HypeSafe operating flow
HypeSafe is designed around a small set of multisig account operations.
1. Connect and sign in
Connect a wallet in the frontend and sign in with a message that proves wallet ownership. This creates a gateway session, but it does not grant the gateway permission to sign business actions.
2. Create or add an account
You can create a new Hyperliquid multisig account from the connected wallet, or add an existing multisig address that your team already operates.
Keep account names clear. HypeSafe is used for shared operations, so every authorized user should be able to identify the account before approving a proposal.
3. Propose an action
Choose a supported template and fill in the required inputs. Typical actions include:
- asset sends;
- withdrawals;
- sub-account operations;
- agent approvals;
- authorized user or threshold updates.
The frontend does not invent task payloads locally. It asks the gateway for the task template and signing payload so every authorized user reviews the same operation.
4. Review and approve
Each authorized user reviews the proposal details and signs from their own wallet. A self-hosted safe-node can also approve if the task matches its local policy.
The gateway verifies each submitted signature and counts it only if it comes from an authorized user of the account.
5. Execute when ready
Once the threshold is met, the selected leader submits the approved action to Hyperliquid. The leader can execute manually from the frontend, or a leader node can execute under local policy.
The result is written back to the gateway so the team can see whether the action was submitted and how it completed.
Optional: run a node
An authorized user can also run safe-node locally. The node signs in to the
gateway with its configured key, pulls tasks for one multisig account, applies
local policy, and signs only when the task is allowed.
Node policy can focus on real fund-management constraints such as destination address allowlists, maximum amounts, allowed template types, and account scope. Tasks outside policy are rejected by default unless the operator explicitly allows them.
The important rule is simple: HypeSafe coordinates approvals, while wallets and self-hosted nodes keep control of signing.