> For the complete documentation index, see [llms.txt](https://docs.tesseract.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tesseract.fi/dedicated-client-vaults/integration-guide/scenario-a.md).

# Scenario A: Manage Your Own Vaults

You're managing DCVs for yourself — treasury, own product, or direct client use. The technical surface is small: one off-chain prerequisite (KYC + whitelisting), a handful of on-chain calls, and the Public API for reporting.

This scenario is organized in the order you'll actually do things:

1. [**Prerequisites: KYC & Whitelisting**](/dedicated-client-vaults/integration-guide/scenario-a/prerequisites.md) — how your wallet gets on the on-chain whitelist.
2. [**Deploying a Vault**](/dedicated-client-vaults/integration-guide/scenario-a/deploying-a-vault.md) — a single transaction against a Vault Deployer.
3. [**Deposits**](/dedicated-client-vaults/integration-guide/scenario-a/deposits.md) — adding capital to an existing vault.
4. [**Instant Withdrawals**](/dedicated-client-vaults/integration-guide/scenario-a/instant-withdrawals.md) — single-transaction withdrawals covered by liquid balance.
5. [**Scheduled Withdrawals**](/dedicated-client-vaults/integration-guide/scenario-a/scheduled-withdrawals.md) — the three-step flow for larger amounts.
6. [**Strategy Assignment**](/dedicated-client-vaults/integration-guide/scenario-a/strategy-assignment.md) — signing an EIP‑712 message to assign a strategy to a fresh vault.
7. [**Reading Vault Data**](/dedicated-client-vaults/integration-guide/scenario-a/reading-vault-data.md) — using the Public API (and the on-chain ERC‑4626 interface) for reporting.

Throughout, code examples are in TypeScript with [viem](https://viem.sh). The same operations work equally well from ethers.js, foundry-cast, Python web3, or any Ethereum tooling — the contracts are standard.

Canonical addresses and method signatures are in [Reference](/dedicated-client-vaults/reference.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 dynamically by asking a question.

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

```
GET https://docs.tesseract.fi/dedicated-client-vaults/integration-guide/scenario-a.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.