> For the complete documentation index, see [llms.txt](https://slabvault.gitbook.io/slabvault-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://slabvault.gitbook.io/slabvault-docs/why-slabvaultfi.md). # Why SlabVaultFi ## SlabVaultFi works because it combines three powerful forces *** ### 🎰 Gacha = Engagement People love the thrill of the unknown. Every pull creates anticipation, excitement, and shared moments. *** ### 🎥 Live = Attention Live streams turn every pull into an event. Moments are shared, clipped, and spread across CT. *** ### 🃏 Real Assets = Credibility These aren’t digital promises. Every pull results in real, graded collectibles stored in the vault. *** ### 🏦 Shared Vault = Retention The vault creates a long-term narrative. As it grows, so does the story—and the reason to stay. *** ### 💎 The Result Entertainment becomes ownership. Attention becomes value. And every participant becomes part of the system. --- # 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://slabvault.gitbook.io/slabvault-docs/why-slabvaultfi.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.