For the complete documentation index, see llms.txt. This page is also available as Markdown.

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 β€” how your wallet gets on the on-chain whitelist.

  2. Deploying a Vault β€” a single transaction against a Vault Deployer.

  3. Deposits β€” adding capital to an existing vault.

  4. Instant Withdrawals β€” single-transaction withdrawals covered by liquid balance.

  5. Scheduled Withdrawals β€” the three-step flow for larger amounts.

  6. Strategy Assignment β€” signing an EIP‑712 message to assign a strategy to a fresh vault.

  7. Reading Vault Data β€” using the Public API (and the on-chain ERC‑4626 interface) for reporting.

Throughout, code examples are in TypeScript with viem. 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.

Last updated

Was this helpful?