> For the complete documentation index, see [llms.txt](https://dasus.gitbook.io/dasus-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dasus.gitbook.io/dasus-docs/start-here/enable-trading.md).

# Enable Trading (Agent Wallet)

Before your first order you complete a one-time step that Dasus calls **Establish Connection** (the terminal button reads **Enable Trading**, Lite reads **Activate trading**). It approves a **session key** — Hyperliquid calls it an agent wallet — that signs your orders in the background, so trading has no wallet popup and no gas. This page explains what you sign, what the key can and cannot do, Hyperliquid's limit on how many keys an account can hold, and how to manage them.

## What you sign, and in which order

Everything is signed with your **main wallet** — the wallet you connected, or the embedded wallet Privy created if you signed in with email. All of them are gas-free signatures, not transactions.

| Signature                         | When                           | What it does                                                                                                                                                                                      |
| --------------------------------- | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Terms of Service**              | First connection of a wallet   | Accepts the Terms, Privacy Policy and Cookie Policy and confirms you are not a U.S. person nor in a restricted jurisdiction (see below)                                                           |
| **Session key** (`approveAgent`)  | **Establish Connection**       | Registers a key generated in your browser as an authorized signer for your account                                                                                                                |
| **Fee cap** (`approveBuilderFee`) | Right after, in the same click | Approves the maximum platform fee Dasus may attach to an order: **1%**, the protocol ceiling for spot. It is a cap, not the fee — see [Fees](https://dasus.gitbook.io/dasus-docs/the-app/fees.md) |

Details that matter:

* The approvals are signed on **Arbitrum**. If your wallet is on another network, the app switches it first; approve the switch if your wallet asks.
* Hyperliquid rejects the session-key approval on an **empty account**. On a new account the app shows **Deposit first**, opens the deposit form, and retries automatically once the deposit is credited — see [Funding Your Account](https://dasus.gitbook.io/dasus-docs/start-here/funding-account.md).
* The session key is what makes trading work. The fee-cap approval is not blocking: if Hyperliquid rejects it at that moment, the app retries it on your first order, and an order is never held back for it.
* **Stay connected** (checked by default) keeps the key in your browser's storage, so the session survives reloads and you do not sign again on every visit.
* The key is generated locally and never sent to Dasus. It is stored per wallet, per browser: another device, another browser profile or cleared site data means a new key and one new signature.

## What the session key can and cannot do

| Can                                                                       | Cannot                                                |
| ------------------------------------------------------------------------- | ----------------------------------------------------- |
| Place, modify and cancel orders (market, limit, stop, TP/SL, scale, TWAP) | Withdraw funds                                        |
| Adjust leverage and margin mode                                           | Transfer funds between balances or to another address |
| Close positions, set TP/SL                                                | Approve other keys or change the fee cap              |
| Register your account under Dasus's Hyperliquid referral code (one time)  | Change the account type                               |

The limit is enforced by Hyperliquid, not by Dasus: agent keys are not granted withdrawal or transfer rights at the protocol level. A compromised key still cannot withdraw, but it could place trades and cause losses — if you ever suspect one, revoke it (below).

## Hyperliquid's limit on session keys

Each browser or device gets its own named key, and Hyperliquid caps how many named keys an account can hold at once. The cap is **not a fixed number**: it grows with the volume the account has traded and is not published — you only learn it when Hyperliquid rejects an approval with *Too many extra agents for cumulative volume traded*.

Dasus avoids it as far as it can: a device reuses the slot it already holds instead of opening a new one, and new sessions take the first free name in the **Dasus 01 … 99** pool. When the cap is still hit, the **Choose which session this device uses** window shows your account's live keys with their role — **This device**, **Session created by Dasus**, **Copy trading engine**, **Another platform** — and the date each one frees up. You pick one of your own Dasus device sessions to reuse and sign once; the device that had it stops trading until it enables its own again. The copy-trading engine's key and keys created by other platforms are never offered, because reusing them would stop your copies or close your session elsewhere. If the engine's key cannot be verified, nothing is offered and the window says so.

{% hint style="warning" %}
**Revoking does not free a slot.** A revoked key becomes unusable, but its slot stays taken until the expiry date shown; approving the same name again resets that date. Slots free up on expiry.
{% endhint %}

## Managing your keys

**Settings → Account → Agent wallets** lists every live key on your account with its role and expiry:

* **Rotate** — generates a new key for this device and approves it under the same name (one signature). Use it after a suspected exposure, or simply for a fresh key.
* **Revoke this device** / **Revoke** — makes that key unusable. Revoking stops orders, copy trading and bots that sign with it until you enable trading again; the key used by the copy-trading engine asks for confirmation and tells you how many copies it stops.
* Keys from other platforms are shown but not touched from here.

Hyperliquid expires session keys on its own — currently about 90 days after approval; the exact date is next to each key. When yours expires, is replaced by another device, or this browser loses it, the terminal simply shows **Enable Trading** again: one signature restores it, with your balances, positions and orders untouched.

## Signing the Terms of Service

The first time a wallet connects, Dasus asks you to read and accept the Terms of Use, Privacy Policy and Cookie Policy, and to confirm you are not a U.S. person and not located in a restricted jurisdiction. You **Sign & Accept** with a gas-free signature. The signed message names the document and its **version** (currently 2.0.0), its **SHA-256 hash**, the URL, the **domain** you are signing on, your wallet, a server-issued nonce and a ten-minute expiry, so the signature cannot be replayed elsewhere or later; the exact text is stored with your acceptance. When the Terms change, the version changes and you are asked to sign again. **Decline** disconnects the wallet.

## Troubleshooting

**"Failed to sign typed data" or the signing prompt errors out.** Make sure the wallet is on **Arbitrum** (approve the switch if it asks), reject any stale pending requests, refresh and try again. With several wallet extensions installed, check the right one is active.

**"Deposit first."** Hyperliquid needs a balance in the account before it registers a session key. Deposit and the setup finishes on its own.

**"Too many extra agents…"** The cap above. Pick one of your Dasus sessions in the window, or wait for the first slot to free up on the date shown.

**Orders say the session is gone / "does not exist".** The key expired, was replaced by another device, or was revoked. Press **Enable Trading** and sign once.

**I revoked my key by mistake.** Press **Enable Trading** and sign again; funds and positions are unaffected.

## Next steps

* New to Dasus? Start with [Getting Started](https://dasus.gitbook.io/dasus-docs/start-here/getting-started.md).
* Ready to trade? See [Order Types](https://dasus.gitbook.io/dasus-docs/trading/order-types.md).
* Questions about costs? See [Fees](https://dasus.gitbook.io/dasus-docs/the-app/fees.md) or the [FAQ](https://dasus.gitbook.io/dasus-docs/help/faq.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://dasus.gitbook.io/dasus-docs/start-here/enable-trading.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
