# 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).