> For the complete documentation index, see [llms.txt](https://docs.bsc.lista.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bsc.lista.org/governance/lista.md). # LISTA LISTA is the governance token for Lista DAO. It allows users to participate in protocol governance, such as raising proposals and voting on them on Lista DAO’s [Snapshot platform](https://snapshot.org/#/listavote.eth). Similar to lisUSD, LISTA token is a medium of exchange in its own right, which can be swapped or put in a farming pool on a DEX at the user’s discretion, e.g. to maximise their capital efficiency, obtain borrowings, and/or compound their yield. Following [LIP-021](https://snapshot.org/#/s:listavote.eth/proposal/0xdb92580e04ca8d688404a689a99579294715bd9ab858cc9b7ba637599720a6ff), 200 million LISTA were permanently locked and the total supply of LISTA has been reduced from 1 billion to 800 million. Check us out on CoinMarketCap [here](https://coinmarketcap.com/currencies/lista-dao/). With the approval of [LIP-024](https://snapshot.org/#/s:listavote.eth/proposal/0x1a15347f6b452049212bdf51ff1a46c0a7edf7ca8efe1004b32c15c2965f0f3b), a new tokenomics was implemented. This upgrade include: * Sunset veLISTA staking model. All staked LISTA can be unlocked without penalty at [this page](https://lista.org/lock). * Protocol revenue previously distributed to veLISTA stakers will now fund $LISTA buybacks, continuing our effort in turning LISTA into a deflationary token. * Emissions previously allocated to veLISTA stakers will continue to support the protocol in the form of funding user rewards, growth initiatives, and ecosystem campaigns. * From now on, all LISTA holders can vote on LIP proposals. The LP pool voting system is wound down as part of this transition. In the future, more benefits will be introduced to LISTA holders. The first on the list is delayed liquidation. Stay tuned for more details. --- # 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://docs.bsc.lista.org/governance/lista.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.