> For the complete documentation index, see [llms.txt](https://piggybank.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://piggybank.gitbook.io/docs/vault-infrastructure/overview.md). # Overview The PiggyBank vault infrastructure is a strategy-agnostic system for managing RWA assets on Solana. It allows vault creation with any underlying asset and provides liquid positions through tokenized shares. Its programs are compatible with Legacy and Token 2022 standard. Vault positions are represented by a liquid token (LT) that shares the same standard and decimals as its underlying. Each vault has its own epoch lifecycle: every time admin reports Net Aset Value (NAV) a new epoch is triggered, previous epoch deposits are withdrawn, and redemptions from previous to last epoch are processed. The Token 2022 vaults are particularly suited for managing RWAs, as it is compatible with the following extensions: * **Scaled UI Amount** - For matching underlying asset stocks splits or income distribution (dividend, coupons...) * **Transfer Hook** - For general compliance requirement and implementing access control on the LTs. ### Key Features Each vault operates independently with its own epoch lifecycle. Positions are represented by liquid tokens that maintain the same standard and decimals as the underlying asset. The system separates vault infrastructure from strategy implementation. This allows: * Any admin to create vaults for their specific strategy * Users to maintain liquid positions they can transfer or trade * Strategies to evolve without infrastructure changes ### Lifecycle Management Each vault has three state accounts tracking: * Vault configuration and totals * Epoch-specific data * Individual redemption records The epoch system ensures orderly processing of deposits and redemptions while the admin manages the underlying assets according to their strategy. --- # 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://piggybank.gitbook.io/docs/vault-infrastructure/overview.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.