Create child vault
Requires key scope escrow/create.
Returns an unsigned v0 transaction for the manager to sign. Do not send payer: the API sets it to the key’s manager and rejects a body that contains it. Unknown fields are ignored. The key’s manager must be the vault’s current on-chain authority, and the vault must be in the key’s allowlist when the key has one. A delegate wallet gets 403.
Child vaults hold part of a parent vault’s capital in a separate account for a separate set of strategies. They share the parent’s authority and deposit mint, take no deposits and have no share mint. The keeper values them as part of the parent, so moving funds inside a family leaves NAV unchanged. Creates a child vault of vault. With fundAmount, the same transaction moves that many deposit-token base units from vault into it. Returns 400 when vault is itself a child vault or already has 16 child vaults. The child’s address comes from the protocol’s next vault id, so a vault that someone else creates first makes this transaction fail. Build again in that case.
Authorizations
Body
Response
Build result. One step. The step adds child, the new child vault's address.
