> 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/lnt-vault/product-design/how-does-lnt-work.md). # How does LNT work Liquid Node Token (LNT) separates assets into **Vesting Token (VT)** and **Yield Token (YT)**. Users deposit their Node NFT into the **LNT Vault**. The Vault calculates and issues **VT (Vesting Tokens)** based on the vesting schedule and expected future rewards associated with the Node license. Simultaneously, the Vault generates a **YT (Yield Token)** for the user. The LNT protocol categorizes node rewards into two buckets: * **Deterministic Rewards**: Pre-defined, calculable yields that users can expect simply by maintaining basic node operation. * **Non-Deterministic Rewards**: Unpredictable or externally contingent rewards such as bonus fees or airdrops. Deterministic future token yields are mapped into **VT** tokens for immediate liquidity, while non-deterministic node earnings are captured via **YT** tokens, which are also liquid. Node license NFTs deposited into the Vault automatically receive deterministic native token rewards (T). These rewards are provided for the systematic redemption of VT. Upon maturity, the remaining Ts are redeemable 1:1 against outstanding VTs. Any surplus (non-deterministic) rewards accrue to YT holders. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://doc.zoofi.io/lnt-vault/product-design/how-does-lnt-work.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.