> For the complete documentation index, see [llms.txt](https://deriverse.gitbook.io/deriverse-v1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://deriverse.gitbook.io/deriverse-v1/vault-mode.md).

# Vault Mode

**Vault Mode** is a security feature that implements a multi-signature authorization system for high-stakes account operations. It involves two roles: the **Account Owner**, who initiates actions, and the **Vault Authority (VA)**, who approves them.

### When to use Vault Mode

Vault Mode is designed for situations where the person trading and the person responsible for the funds are not the same, or where trading activity needs to stay inside pre-agreed limits.

* **Algorithmic trading** - run automated strategies from the Owner wallet while the Vault Authority caps which markets the algo can touch and approves every withdrawal. A compromised key or a misbehaving strategy still cannot move funds off the platform.
* **Delegated execution** - give a trader access to execute while a risk manager or partner holds the VA wallet, keeping segregation of duties between execution and custody.
* **Fund and DAO treasuries** - restrict trading to an approved instrument list and route every withdrawal through a second signer, with permitted destination addresses set in the withdrawal whitelist.
* **Prop desks** - limit each trader to a defined set of instruments and Spot/Perp permissions, adjustable in real time.

### 1. Onboarding: creating your vault

When you first navigate to the Vault Mode page, you are guided through a setup process to prepare your account for enhanced security.

* **Starting the process** - a modal titled **Create a Vault** appears. Click **Start** to begin the step-by-step onboarding.
* **Feature overview** - the onboarding introduces the core security concepts: delegating account authority, managing trading whitelists, confirming withdrawals, and restricting DeFi access.
* **Finalizing access** - to unlock the Vault Mode interface and move to the activation stage, click **Open Vault Mode** on the final step.
* **Skipping** - you can close the onboarding modal at any time by clicking the **X** icon in the corner.

### 2. Understanding roles

| Role                     | Capabilities                                                                                                                                                  |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Account Owner**        | The original creator of the Deriverse account. Only the Owner can initiate activation, deactivation, and withdrawal requests.                                 |
| **Vault Authority (VA)** | A trusted second wallet assigned by the Owner. The VA can approve or reject activation and deactivation, manage trading permissions, and approve withdrawals. |

{% hint style="info" %}
The Vault Authority **cannot trade** on the Owner's behalf.
{% endhint %}

### 3. Activation and deactivation

To secure your account, you must link it to a Vault Authority.

#### Activating Vault Mode

1. The Owner navigates to **Vault Mode → Owner** and clicks **Activate**.
2. The Owner enters the valid wallet address of their chosen **Vault Authority**.
3. The status becomes **Activating**. The VA then sees a **Pending Activation** request in their dashboard.
4. Once the VA signs the confirmation in their wallet, the status becomes **Active**.

#### Deactivating Vault Mode

1. The Owner initiates deactivation through the **Owner** tab.
2. The status changes to **Deactivating** and a request is sent to the VA.
3. The VA must confirm and sign the deactivation for the account to return to **Inactive** (base) status.

### 4. The trading whitelist

In Vault Mode, the VA controls exactly which markets the Owner can access.

* **Instrument limits** - a whitelist can contain a maximum of **8 instruments**.
* **Permissions** - for each instrument, the VA sets **Spot** and **Perp** access independently using toggle switches:
  * **Green check** - trading is allowed.
  * **Red cross** - trading is blocked.
* **Real-time enforcement** - if the VA removes an instrument or blocks a permission, the Owner is immediately prevented from submitting new orders for that market.

### 5. Withdrawal approval flow

Withdrawals in Vault Mode are not instantaneous - they require a "four-eyes" check.

1. **Request** - the Owner creates a withdrawal request for a specific token and amount.
2. **Pending state** - the request appears as **Pending** in both the Owner's and the VA's dashboards.
3. **VA approval** - the Vault Authority reviews the details and clicks **Confirm Withdrawal**.
4. **Completion** - after the VA signs the transaction, the funds are released.

{% hint style="warning" %}
Only **one pending withdrawal** is allowed at a time. The Owner can cancel a pending request at any point before VA approval.
{% endhint %}

### 6. Vault Authority dashboard

A single wallet can serve as the Vault Authority for **multiple Owners**.

For institutional or highly secured setups, the VA can access the **Advanced** section:

* **Withdrawal whitelist** - the VA can define a specific list of permitted destination addresses.
* **DeFi whitelist** - the VA can manage access to external DeFi protocols, such as Kamino.