> For the complete documentation index, see [llms.txt](https://docs.creditcoop.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.creditcoop.xyz/user-documentation/v2/vaults.md). # Vaults A Vault is a pooled smart contract structure that accepts stablecoin deposits and allocates capital across Credit Lines and sources of liquid asset yield within the Credit Coop Protocol. Vaults are non-custodial. CMBT Labs does not hold, control, or have access to Digital Assets deposited into any Vault at any time. *** ### How Vaults work Vault Depositors supply Digital Assets to a Vault through the Interface. Upon deposit, they receive Vault Tokens representing their pro rata participation, redeemable for the underlying stablecoin subject to available liquidity. Capital within the Vault is allocated by the Vault Curator across Credit Lines and other liquidity strategies. Vault Depositors do not control individual allocations — that responsibility sits with the Curator. *** ### Protocol parameters and governance Vault-level configuration and protocol-level parameters — including fee structures, collateral requirements, and credit limits — are determined by Credit Coop Protocol governance processes and encoded in smart contract logic. No single party, including CMBT Labs, has unilateral control over these parameters. Current Vault and Credit Line configurations are displayed on the Interface at [app.creditcoop.xyz](https://app.creditcoop.xyz). *** ### Related pages * Participants & Roles — responsibilities of Vault Depositors, Curators, and Borrowers * Fees — fee types applicable to Vaults * Servicer & Liquidation — how liquidation works --- # 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.creditcoop.xyz/user-documentation/v2/vaults.md?ask=&goal= ``` `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.