Frontend

safe-frontend is the human operating surface for HypeSafe.

It is where signers connect wallets, sign in, manage tracked accounts, review proposals, approve or reject actions, and execute approved tasks when they are the selected leader.

The frontend is designed for inspection. Before a signer approves, it should be clear which account is being used, what action is being requested, who the leader is, and what payload will be signed.

Responsibilities

• Connect wallets through the browser.
• Sign in with a wallet signature and use the gateway-issued session.
• Create a new Hyperliquid multisig account or add an existing multisig account.
• Render task templates and collect user inputs.
• Ask the gateway for signing payloads instead of constructing them locally.
• Let signers approve or reject tasks from their own wallet.
• Let the leader submit an approved multisig action to Hyperliquid and write the result back to the gateway.

Boundary

The frontend is not the source of truth for templates, payloads, or approval counts. Those come from the gateway. The frontend is the place where humans inspect intent and choose whether to sign.

The frontend also does not custody keys. Wallet signatures happen in the connected wallet, and execution still requires the selected leader to submit the approved action.

When It Is Used

Every team uses the frontend for onboarding, account visibility, proposal creation, manual review, and manual execution. Even teams that run safe-node still use the frontend to understand the shared account state.