> For the complete documentation index, see [llms.txt](https://goldilocks-1.gitbook.io/goldidocs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://goldilocks-1.gitbook.io/goldidocs/yield-splitting-vaults/basics.md). # Basics Goldilocks' yield splitting vaults enable users to trade the future earnings of yield bearing positions on Berachain's bluechip defi protocols and native infrastructure. Users can deposit assets into a yield splitting vault, and the vault will automatically use the assets to create yield bearing positions on supported platforms. The user will receive (i) ownership tokens representing ownership of the deposited assets, and (ii) yield tokens representing ownership of the yield that those assets generate over the remaining lifetime of the vault. The user is then able to trade those tokens on partner platforms, thereby immediately unlocking the liquidity of the future yield generated by their assets. --- # 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://goldilocks-1.gitbook.io/goldidocs/yield-splitting-vaults/basics.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.