> For the complete documentation index, see [llms.txt](https://sparklexai.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sparklexai.gitbook.io/docs/core-concepts/the-vaults/earning-vault.md). # Earning Vault Earning Vaults gather deposits for a given asset (ETH, wBTC, USDC, RWAs and more) into a single optimized contract. Once inside, funds can enter a looping strategy — borrow → buy → restake → repeat — to amplify yield while guardrails keep leverage in check. \ The AI watches yield spreads, borrow costs, LTV thresholds, and gas. If the spread narrows or safety thins, loops unwind automatically before risk builds. When conditions improve, they rebuild. \ Every deposit is tracked individually. You receive a vault receipt token (YBT-style) that reflects your share and grows with earnings. Return it any time to withdraw principal plus yield. \ **Why users choose Earning Vaults?** * Auto-loop and auto-de-loop based on live yield and risk signals * Block-level compounding of all income streams * Immutable custody layer — strategies can evolve, contract rules cannot \ Looking ahead: governance over strategy parameters will migrate to a DAO in a future release; the underlying custody contract stays fixed and non-custodial. --- # 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://sparklexai.gitbook.io/docs/core-concepts/the-vaults/earning-vault.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.