HypeSafe

Node

safe-node - self-hosted signer and risk-control node

safe-node is an optional local signing and risk-control service for HypeSafe.

It is not a Node.js service and not a blockchain node. It is a Rust daemon/CLI that an operator runs with a local encrypted signer keystore.

The node exists for teams that want signer-side automation without transferring signing authority to the gateway.

Responsibilities

  • Sign in to the gateway with the configured signer.
  • Track one configured multisig account.
  • Pull signing tasks from the gateway inbox.
  • Apply local policy before signing.
  • Submit approval signatures or rejection votes back to the gateway.
  • If the local signer is the configured leader, pull executable tasks, submit allowed actions to Hyperliquid, and write results back to the gateway.
  • Keep local SQLite state so it can avoid duplicate execution after restarts.
  • Expose read-only debug HTTP and a terminal UI for local observation.

Default Policy Shape

The first node policy focuses on withdrawal automation:

  • the task must belong to the configured multisig account;
  • the task leader must match the configured leader;
  • the template must be in allowed_templates;
  • the withdrawal amount must be at or below withdraw_limit.

Tasks outside policy are rejected or ignored. The node does not fetch signing payloads, sign, submit to Hyperliquid, or write successful results for rejected tasks.

When to use it

Use safe-node when an owner wants local automation, spending limits, or leader execution controlled by infrastructure they operate.

Do not use safe-node as a shortcut around review. It should encode policy that a signer is comfortable enforcing automatically.

Boundary

safe-node only controls its own local signer. It cannot bypass the multisig threshold and it cannot make the gateway sign for anyone. The gateway still verifies every node signature before counting it.

Teams should run a node when they want signer-side automation under their own infrastructure and policy. Teams that only need manual approval can use the frontend and gateway without running a node.