> For the complete documentation index, see [llms.txt](https://docs.lifinity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lifinity.io/flares/lfnty-allocation.md). # LFNTY Allocation 1,000,000 LFNTY (1% of the total supply) was reserved for Flare holders and has been distributed as of May 16, 2023. Flares could either be staked or locked to receive their portion of LFNTY. Staking allowed holders to earn a pro-rata share of the remaining LFNTY to be distributed over the course of 1 year. Holders could unstake at anytime. Locking Flares granted holders their share of LFNTY as 4-year locked veLFNTY upfront. The Flare was locked until the end of the 1 year distribution period. The amount of LFNTY that was locked for veLFNTY was 1/10,000 of the LFNTY that was left to be distributed at the time that it was locked (e.g. if you locked 6 months after distribution had begun, you would have received 1/10,000 of 0.5%). --- # 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.lifinity.io/flares/lfnty-allocation.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.