Signers, Wallets, and Control
How Pakt approval, restricted signing, custody, and venue access stay separate.
Your Pakt signer approves and disables Pakts. It is implemented as a recoverable wallet, but its product role is signing lifecycle decisions. We call it a signer so it is not confused with wallets that hold funds or access a venue.
Pakt uses a separate restricted execution signer for agent actions. It can sign an exact request only after Pakt proves that the request satisfies your active rules.
| Role | What it can do |
|---|---|
| You | Control the Pakt signer, approve or disable Pakts, manage permissions, recover the underlying wallet, and withdraw directly |
| Pakt signer | Sign your exact activation or disable decision in the dashboard |
| Your AI agent | Draft rules, prepare review links, propose actions, and submit authorized requests |
| Restricted execution signer | Sign only the exact agent requests that Pakt authorizes |
| Pakt | Check actions and authorize only the exact requests that pass |
| Wallet provider | Protect the underlying wallet keys and enforce signer permissions |
Your agent never receives either signer's private key. Connecting an agent over MCP does not let it approve its own Pakt or change signer permissions.
Hyperliquid Uses Two Wallets
Your existing Hyperliquid master wallet approves the execution wallet underlying your Pakt signer as a trading agent. The master wallet remains outside Pakt.
This venue approval is separate from connecting your AI agent and activating a Pakt. All required setup must be complete before live trading is available.
Keep Control of Your Funds
You can recover or export your wallet and withdraw directly without the Pakt backend. You can also remove Pakt's restricted execution signer from the underlying wallet or revoke the Hyperliquid agent approval from your master wallet.
Disabling a Pakt stops that individual root. Removing a signer or revoking venue access changes a broader permission. Neither undoes actions that have already executed.