Clear account operations
Create or add multisig accounts, prepare treasury and account-management actions, and keep signers aligned around one canonical task view.
What HypeSafe provides
A shared operating layer without shared custody
HypeSafe connects human operators, a keyless coordination gateway, and optional self-hosted signing nodes into one approval flow for Hyperliquid multisig accounts.
Threshold approvals
Every proposal is turned into a fixed EIP-712 payload. The gateway verifies signer identity, tracks approvals and rejections, and shows execution readiness.
Signer-side automation
Teams that need automation can run safe-node with local policy for selected templates, limits, accounts, and leader execution.
No HypeSafe custody
Private keys remain in browser wallets or operator-run nodes. The gateway coordinates state and history, but it cannot sign for users.
From proposal to execution
The same task record follows the action from intent capture to signature collection and final Hyperliquid submission.
Intent
Create a proposal
An operator selects the account, action template, inputs, and leader before the first signature is requested.
Canonical
Freeze the signing payload
The gateway binds the account, nonce, network, leader, template, and inputs into one payload for every signer.
Threshold
Collect approvals
Wallets and allowed nodes submit approvals or rejections; the gateway verifies each signer before updating progress.
Automation
Apply local policy
Self-hosted nodes approve only actions that match the operator's configured accounts, templates, and limits.
Execution
Execute on Hyperliquid
After threshold approval, the leader submits the multisig action to Hyperliquid and the result is recorded for the team.
Intent
Create a proposal
An operator selects the account, action template, inputs, and leader before the first signature is requested.
Canonical
Freeze the signing payload
The gateway binds the account, nonce, network, leader, template, and inputs into one payload for every signer.
Threshold
Collect approvals
Wallets and allowed nodes submit approvals or rejections; the gateway verifies each signer before updating progress.
Automation
Apply local policy
Self-hosted nodes approve only actions that match the operator's configured accounts, templates, and limits.
Execution
Execute on Hyperliquid
After threshold approval, the leader submits the multisig action to Hyperliquid and the result is recorded for the team.
Intent
Create a proposal
An operator selects the account, action template, inputs, and leader before the first signature is requested.
Canonical
Freeze the signing payload
The gateway binds the account, nonce, network, leader, template, and inputs into one payload for every signer.
Threshold
Collect approvals
Wallets and allowed nodes submit approvals or rejections; the gateway verifies each signer before updating progress.
Automation
Apply local policy
Self-hosted nodes approve only actions that match the operator's configured accounts, templates, and limits.
Execution
Execute on Hyperliquid
After threshold approval, the leader submits the multisig action to Hyperliquid and the result is recorded for the team.
Intent
Create a proposal
An operator selects the account, action template, inputs, and leader before the first signature is requested.
Canonical
Freeze the signing payload
The gateway binds the account, nonce, network, leader, template, and inputs into one payload for every signer.
Threshold
Collect approvals
Wallets and allowed nodes submit approvals or rejections; the gateway verifies each signer before updating progress.
Automation
Apply local policy
Self-hosted nodes approve only actions that match the operator's configured accounts, templates, and limits.
Execution
Execute on Hyperliquid
After threshold approval, the leader submits the multisig action to Hyperliquid and the result is recorded for the team.
Frequently asked questions
Answers for teams assessing HypeSafe for shared Hyperliquid operations.
Who is HypeSafe for?
HypeSafe is for teams that manage Hyperliquid accounts with multiple people or operational roles, and need a clearer way to propose, approve, and execute actions without concentrating control in one wallet.
Is HypeSafe custodial?
No. HypeSafe does not hold private keys or sign business actions. Signatures come from wallets or self-hosted nodes controlled by each signer.
What does safe-node add?
safe-node lets a signer automate approvals and leader execution under local policy. It is optional; teams can use HypeSafe fully with browser-wallet approvals.