> For the complete documentation index, see [llms.txt](https://docs.sierra.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sierra.money/protocol-use-cases/issuing-a-liquid-vault-token.md). # Issuing a Liquid Vault Token **Designed For:** DeFi applications, stablecoin issuers, exchanges, consumer platforms and trading protocols wanting to distribute a yield-bearing asset with full DeFi composability A Liquid Vault Token (LVT) is a permissionless Vault upgraded with the infrastructure needed for permissionless secondary market activity and composability: * LayerZero OFT for cross-chain distribution * RedStone fundamental oracles for onchain NAV feeds * Network of [Authorized Participants](/additional-resources/authorized-participant-onboarding.md) arbitraging secondary market liquidity through minting and redemptions * 24/7 threat detection monitoring with Hypernative Once fully deployed, the LVT is ready for all forms of utility across CeFi and DeFi. As an issuing partner, you get Sierra's institutional stack with the distribution capabilities of a fully composable, yield-bearing asset. SIERRA, the flagship LVT of the Sierra Protocol, became one of the fastest growing LVTs on [Stablewatch](https://www.stablewatch.io/analytics) with this same infrastructure. --- # 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.sierra.money/protocol-use-cases/issuing-a-liquid-vault-token.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.