> For the complete documentation index, see [llms.txt](https://doc.lockerprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.lockerprotocol.com/hyper-agentic-trader/mandate.md).

# The mandate

The limits you sign in your wallet, which the guardian checks before every opening.

The policy lives on your computer: anyone with a shell there can edit it, and a wider limit waits for your password. The **mandate** is the same kind of limits, signed by your account in your wallet, which no program on the computer can sign for you. With Locker Vault, the safest, they are signed on an offline phone that no program on the computer can reach.

```sh
lpa mandate sign --actions trade,pilot --max-notional-per-day 500 --preview
lpa mandate sign --actions trade,pilot --max-notional-per-day 500
lpa mandate show
lpa mandate revoke
lpa mandate release
```

{% hint style="info" %}
**Read it before your wallet sees it.** `lpa mandate sign --preview` says the mandate as it would be signed now: its rows, the payload your wallet is shown byte for byte, and who may place an order without asking under it. It asks no one, signs nothing and writes nothing, and every refusal the signing would give it gives the same way.
{% endhint %}

## What it binds

The mandate takes the policy's bounds as they stand, and adds what the policy has no word for.

| Bound                                       | Comes from                                                                                                                                                |
| ------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Largest order                               | the policy                                                                                                                                                |
| Highest leverage                            | the policy                                                                                                                                                |
| Markets, dexes                              | the policy                                                                                                                                                |
| Orders per day                              | the policy                                                                                                                                                |
| **Opened per day, at most**                 | `--max-notional-per-day`, in notional, 10 or more. Default: the policy's largest order times its orders per day                                           |
| **Service fee, at most, and its recipient** | the one rate and the one address the agent may ever pay                                                                                                   |
| **Allowed uses**                            | `--actions`: `trade` (orders from the agent), `copy` (live copies of the traders it names), `pilot` (orders the pilot decides itself, without asking you) |
| **Traders copied, and the copy budget**     | `--copy-leaders` (10 at most) and `--copy-budget` (USD all live copies share)                                                                             |
| **Valid until**                             | `--days`, 180 at most and the agent key's own end by default: never past that end, nor past the policy's own end when it has one                          |

The guardian applies the **narrower** of the mandate and the policy. Nothing on the computer widens the mandate, the daily pilot's charter and the strategy in use included: `lpa pilot strategy show --name <name> --equity <usd>` says what the mandate in force would refuse of a strategy, order by order, before any day plays it.

{% hint style="info" %}
**One term for everything.** The mandate ends with the agent key, 180 days at most and never past it, and the service keeps the key for that same life: the renewal of the key is the gesture that brings your wallet back to read the limits. It used to be thirty days, so that the wallet had its say every month, and a mandate that ended five months before its key stopped a pilot nobody had decided to stop. A shorter mandate is still yours to sign: `lpa mandate sign --days 30`.
{% endhint %}

## What the guardian checks, before every opening

* The signature is this account's, and the agent named is this agent.
* The mandate has not ended, has not been revoked, and is not older than the last one signed here.
* It is of the form this version reads: fifteen fields under the version `2` of its domain since lpa 2.4.0. One signed before, which carried a daily loss limit, is refused whole by `MANDATE_OUTDATED` until your wallet signs a new one; closing stays allowed.
* The use is allowed: the continuous pilot live needs `pilot`, a live copy needs `copy` and its own trader named, and the daily pilot's live day signs as `trade`.
* Today's notional, plus this order, is at or under the ceiling.
* The service fee the orders carry is the rate and the recipient the mandate names, and no more.
* The narrowest of the policy and the mandate.

Closing a position is always allowed, whatever the mandate says.

## How your wallet shows it

The terminal lists the bounds and asks. The ceremony page shows the same rows. Then, with Locker Vault, the Vault shows the same bounds again, as a card of its own on its signature page, in its own words: the main dex reads *Hyperliquid* there, and the card ends with the instant the mandate was signed. The terminal's list:

```
  Account                            0x3f5CE5FBFe3E9af3971dD833D26bA9b5C936f0bE
  Signed                             2026-09-30 09:30 UTC
  Agent key                          0x9d7948065e7dbddfb2013c1d71293eeafe8ecac9
  Allowed                            orders from the agent, and copies of the traders below
  Largest order                      $100.00
  Highest leverage                   3x
  Markets                            any market
  Dexes                              main
  Orders per day                     20
  Opened per day, at most            $500.00
  Service fee, at most               0.05%
  Fee recipient                      0x49ed7ce9110faa241444dec2b61a1f1651f57517
  Traders copied                     0x5b5d51203a0f9079f8aeb098a6523a13f298c060
  Copy budget                        $250.00
  Valid until                        2026-10-07 09:30 UTC
Sign this mandate with Locker Vault? [y/N]
```

With another wallet, the last line says *with your browser extension* or *with your mobile wallet*.

**Read those rows in your wallet.** The Vault warns you when copies or the pilot will place orders without asking you, when the mandate allows a use the device cannot explain, and when it names an account other than the one signing.

A browser extension or a mobile wallet shows the mandate as raw fields, with no card of its own. So the page shows them first, field by field, each value explained in one line: compare each field your wallet shows with that list before you approve.

A mandate that allows `pilot` is kept only once that use was explained to you. With the Vault, its card explains it, and the terminal asks after the signature whether your phone did: answer no and nothing is kept; update the Vault, then sign again. An extension or a mobile wallet shows only the word, so `lpa` explains it itself and asks your yes before the request leaves: *Under this mandate the pilot places and closes orders by itself, without asking you, within the limits above; your wallet shows only the word pilot. Send it to your wallet to sign?* A mandate signed with a use this version of `lpa` does not know is refused by name: *This mandate allows 'pilot', which this version of lpa does not know. Update lpa.*

The signature is checked on the computer before the file is written, whatever signed it. An answer signed by another account is refused (`MANDATE_INVALID` from another Vault, `VAULT_ANSWER_MISMATCH` from an extension or a mobile wallet). The guardian bounds the agent the same way whichever wallet signed the mandate.

## Where it is kept, and why it cannot be rolled back

```
~/.lpa/mandate.json          the mandate and its signature
~/.lpa/mandate-state.json    the highest nonce signed here, and the revocation
```

Both files are private to your user. The two marks in `mandate-state.json` only ever go **up**. So a mandate file that is gone, damaged, older than the last one signed, revoked, ended, or signed for another agent opens nothing, by name, until your wallet signs a newer one. Putting an old file back changes nothing.

`lpa unlock` and `lpa status` say which of those cases you are in. In JSON, `lpa mandate show` gives a `state` of `in force`, `ended`, `other agent`, `invalid`, `removed`, `older`, `revoked`, `outdated` (signed before lpa 2.4.0) or `none`, with the marks.

## Renew, revoke, release

| Command               | What it does                                                                          | Who can run it                       |
| --------------------- | ------------------------------------------------------------------------------------- | ------------------------------------ |
| `lpa mandate sign`    | signs a new mandate in your wallet. A new one replaces the old                        | you, at a terminal, with your wallet |
| `lpa mandate show`    | reads it back and says whether it is in force                                         | anyone, including an agent           |
| `lpa mandate revoke`  | durably refuses every mandate up to this one. Only restricts, so it needs no password | anyone, including an agent           |
| `lpa mandate release` | drops the mandate **and the marks**, so the local policy alone bounds the agent again | you, with your password              |

After `lpa agent renew` or a new `lpa init`, the old mandate opens nothing for the new agent, and the command says so: sign a new one.

{% hint style="warning" %}
**What the mandate does not do.** It binds the guardian, not the key. A program that reads the guardian's memory, or steals the sealed key and its password, can talk to Hyperliquid without the guardian, and no file on your computer stops it. The agent key's own limits still hold then: no withdrawal, no send. A program running as your user can also delete every file of the folder, marks included, and then `lpa unlock` says "no mandate" where you signed one. That sentence is your cue.
{% endhint %}

## Learn more

* [Go live under the mandate](https://doc.lockerprotocol.com/hyper-agentic-trader/go-live.md)
* [The guardian and the keys](https://doc.lockerprotocol.com/hyper-agentic-trader/guardian-and-keys.md)
* [lpa mandate, in the command reference](https://doc.lockerprotocol.com/hyper-agentic-trader/commands/mandate.md)
* [What the Vault shows for Hyperliquid](https://doc.lockerprotocol.com/vault/sign-a-transaction/hyperliquid.md)
