> For the complete documentation index, see [llms.txt](https://docs.lumoz.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lumoz.org/verifier/verifer-node-explained/license.md). # License License is the official recognition of Verifier Node identity, serving as a necessary binding condition when setting up a Verifier Node. To ensure the quality and decentralization of the protocol, we have set a limit of 100,000 licenses. These licenses exist in the form of non-fungible tokens (NFTs), ensuring the uniqueness and non-replicability of each license. The introduction of NFTs not only provides secure digital ownership proof for licenses but also allows licenses to be freely transferred among users. This flexibility gives users complete control over Verifier Nodes, enabling them to buy, sell, or transfer their licenses according to market demand and personal preferences. Importantly, when a Verifier Node transfers its held license to another party, the node will no longer be eligible to receive any form of reward from the Lumoz network. This mechanism aims to encourage long-term network participation and contribution while ensuring fairness and transparency in network reward distribution. Through the License system, the Lumoz network aims to establish a stable, efficient, and user-friendly environment for Verifier Node operation. We welcome and encourage active participation from the global community to collectively maintain and promote the continuous development and prosperity of the Lumoz ecosystem. --- # 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.lumoz.org/verifier/verifer-node-explained/license.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.