# Managing DCVs

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**](https://docs.tesseract.fi/dedicated-client-vaults/integration-guide/scenario-a/prerequisites) — how your wallet gets on the on-chain whitelist.
2. [**Deploying a Vault**](https://docs.tesseract.fi/dedicated-client-vaults/integration-guide/scenario-a/deploying-a-vault) — a single transaction against a Vault Deployer.
3. [**Deposits**](https://docs.tesseract.fi/dedicated-client-vaults/integration-guide/scenario-a/deposits) — adding capital to an existing vault.
4. [**Instant Withdrawals**](https://docs.tesseract.fi/dedicated-client-vaults/integration-guide/scenario-a/instant-withdrawals) — single-transaction withdrawals covered by liquid balance.
5. [**Scheduled Withdrawals**](https://docs.tesseract.fi/dedicated-client-vaults/integration-guide/scenario-a/scheduled-withdrawals) — the three-step flow for larger amounts.
6. [**Strategy Assignment**](https://docs.tesseract.fi/dedicated-client-vaults/integration-guide/scenario-a/strategy-assignment) — signing an EIP‑712 message to assign a strategy to a fresh vault.
7. [**Reading Vault Data**](https://docs.tesseract.fi/dedicated-client-vaults/integration-guide/scenario-a/reading-vault-data) — 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](https://docs.tesseract.fi/dedicated-client-vaults/reference).