Pakt Lifecycle
Drafts can change. Active rules are fixed. Only you can disable or re-enable a Pakt.
A Pakt becomes usable only after your Pakt signer approves it. You approve Pakts you or your agent draft in the dashboard. The default trading Pakt that new accounts receive is approved by the same signer during account setup, without a wallet prompt or a separate review step. New full-access accounts that keep it also receive a default spending Pakt, approved the same way the next time the dashboard opens; accounts created before it was introduced do not.
| State | Meaning |
|---|---|
| Draft | Rules for review; no authority to act |
| Active | Approved rules that may be used when account and venue requirements are satisfied |
| Disabled | Unavailable for new authorizations until you approve re-enabling it |
A review link is a request for your decision, not another active state. Preparing a link or letting it expire leaves the current lifecycle unchanged.
Changing Rules
An active Pakt cannot be edited. An account can have one active trading Pakt (Hyperliquid or Gateway, not both), one active services Pakt and one active payments Pakt. A Gateway Pakt also cannot be active together with a payments Pakt or a paying services Pakt, such as the default spending Pakt. To change its rules, draft a replacement with a new root, disable the current root, wait for its outstanding authorization window to close, and then activate the replacement. Activation never disables another Pakt implicitly.
A disabled root can be re-enabled with a fresh approval from your Pakt signer, after the same short wait. It keeps its root, receipts and history; only the current approval changes. Activation and re-enabling apply the current admission rules: a root committed to a retired policy program, or with a rule at a scope its program never checks, keeps running while it stays active but cannot be activated or re-enabled; draft a replacement instead. Future Hyperliquid subaccounts will be separate execution scopes, allowing each subaccount to carry its own active Pakt and risk frontier.
For the browser steps, including expired links and interrupted approvals, see Activate or Disable a Pakt.