> For the complete documentation index, see [llms.txt](https://docs.vena.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vena.finance/points-and-incentives/earning-vena-points.md). # Earning Vena Points Vena Points are Vena's internal points system. They accrue to users as they use the protocol. At $VENA TGE, Vena Points convert into $VENA tokens. ## How Vena Points are earned Vena Points accrue from on-protocol activity. Broadly: * **Supplying** assets to Vena markets. * **Borrowing** against supplied collateral. * **Position duration**: points continue to accrue as long as a position is open. * **General dapp use**: interacting with the Vena dapp contributes to the Vena Points balance alongside supply and borrow activity. Vena Points are awarded on a **biweekly schedule**. Exact multipliers, decay behaviour, and any launch boosts are not published. The dapp displays a running Vena Points balance for connected wallets. ## What Vena Points unlock Vena Points convert into $VENA tokens at $VENA TGE. --- # 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.vena.finance/points-and-incentives/earning-vena-points.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.