# Trader delegation

The **trader** is a separate address the manager authorises to execute trades on the vault's behalf. It's how managers run a vault without signing every transaction from the manager wallet — useful for API bots, automated strategies, and [AI-assisted management](/manage/ai-assisted-management.md) via MCP.

A trader can move the vault's assets within the rules. A trader **cannot** change fees or rotate the manager address — those stay with the manager. Neither the trader nor the manager can withdraw depositor funds; the vault contract doesn't allow that. Everything the trader does still passes through the [Guard System](/security/guard-system.md) — same enabled assets, same protocol allowlist, same constraints as the manager.

## Set Trader

Open your vault in the [Chamber app](https://chamberfi.com/) and go to vault settings → **Set Trader**.

You configure three things:

* **Trader address.** One address. Paste the wallet you want to delegate to. Replacing it overwrites the previous trader — there's only ever one active trader per vault.
* **Trader can change vault assets.** **On by default.** When on, the trader can both execute trades **and edit the vault's enabled assets** — adding new supported assets or removing unused ones, within the same rules the manager follows (e.g. can't remove an asset the vault currently holds). This is broader than "swapping between held assets": a trader with this toggle on can enable an asset you haven't explicitly approved and route funds into it. Turn this off if you want the trader restricted to trading within the assets *you've* enabled.
* **Trader can toggle vault privacy.** **Off by default.** Lets the trader flip the vault between public and private. Most managers leave this off; only enable it if the trader is a trusted automation that needs to gate deposits on its own schedule.

Confirm the transaction from your manager wallet to apply.

Because the default is on, most trader setups today allow the trader to change enabled assets. If that's not what you want, turn it off explicitly before authorising the trader.

## What the trader can and cannot do

| Action                                                | Manager | Trader                               |
| ----------------------------------------------------- | ------- | ------------------------------------ |
| Execute trades on enabled assets                      | Yes     | Yes                                  |
| Use approved protocols (swaps, LP, lending, leverage) | Yes     | Yes                                  |
| Edit the vault's enabled assets (add/remove)          | Yes     | Yes (if "change vault assets" is on) |
| Flip vault privacy (public ↔ private)                 | Yes     | Only if toggle is on                 |
| Set vault maximum supply cap                          | Yes     | Yes                                  |
| Change fees                                           | Yes     | No                                   |
| Change minimum deposit                                | Yes     | No                                   |
| Rotate the manager address                            | Yes     | No                                   |
| Access or withdraw depositor funds                    | No      | No                                   |

The trader role is scoped to operational work. Anything that changes the vault's rules stays with the manager.

## Creating a trader wallet

The trader wallet is just a standard EOA (externally owned account) — any wallet you control. Common patterns:

* **A fresh wallet you generate yourself** (e.g. via MetaMask, a hardware wallet, or a key generated in a secure environment). This keeps your manager wallet out of the hot path for trading.
* **A server-side wallet** for an API bot or custom strategy.
* **The wallet provisioned during** [**AI-assisted management**](/manage/ai-assisted-management.md) — the MCP flow uses the same trader-delegation mechanic under the hood.

Treat the trader key with the same care as any trading key. It can move vault assets, and there's no revocation without rotating it.

## Rotating or revoking the trader

To rotate: open **Set Trader**, paste the new address, confirm. The previous trader immediately loses the ability to trade.

To revoke entirely: use **Remove Trader** in vault settings. That clears the trader address and disables the trader role until you set a new one. (You can't revoke by pasting `0x0000...0000` into Set Trader — the contract rejects the zero address there. Remove Trader is the correct path.)

Rotate if you suspect the trader key is compromised, if you're retiring a bot, or if you're switching from one AI agent setup to another.

## Typical patterns

* **Manual-only manager.** Don't set a trader. Sign every trade from the manager wallet. Simplest, slowest.
* **AI-assisted.** Set a trader wallet, hand its key to the [MCP flow](/manage/ai-assisted-management.md). Keep privacy toggle off.
* **Automated bot.** Set a trader wallet the bot controls. Keep privacy toggle off unless the bot genuinely needs it.
* **Mixed.** Any of the above, plus the manager still trades manually whenever. The trader doesn't lock the manager out.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.chamberfi.com/manage/trader-delegation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.