Concepts
Core concepts behind HypeSafe accounts and approvals
This section explains the account model, approval flow, and architecture behind HypeSafe.
HypeSafe follows three principles:
- Secure default: shared actions require approval from the configured owners before execution.
- Operational clarity: every action is represented as a proposal with a fixed signing payload and visible approval state.
- Signer-side control: keys remain in wallets or self-hosted nodes, while the gateway only coordinates and verifies.
Topics
- Architecture: how the frontend, gateway, node, and Hyperliquid execution layer fit together.
- Multisig: owners, thresholds, proposals, approvals, and leader execution.
- Vision: why HypeSafe is built around shared control without shared custody.