> For the complete documentation index, see [llms.txt](https://doc.zoofi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.zoofi.io/lvt-vault/introduction-to-lvt.md).

# Introduction to LVT

LVT（Liquid Vesting Token）is a smart new way to make locked-up tokens in crypto projects tradeable right away, without breaking the rules or the project's long-term plans. Think of it like turning a "promise" for future tokens into something you can buy, sell, or hold on exchanges today. It works by creating special tokens called VT (Vesting Tokens) that represent your share of those future releases—based on real vesting schedules from project teams or legal deals like SAFTs. For example, if a project has 1 million tokens set to unlock over two years, LVT lets them "mint" VT upfront, so the team can sell some at a discount to raise cash early for building. Buyers get in cheap, then cash out for full value when the real tokens drop. It's all handled by secure smart contracts that check everything, keeping things fair and compliant. This builds on ideas from node-based models but fits perfectly for vesting, helping everyone—teams, investors, and fans—get liquidity without the old headaches.


---

# 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://doc.zoofi.io/lvt-vault/introduction-to-lvt.md?ask=<question>&goal=<endgoal>
```

`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.
