> For the complete documentation index, see [llms.txt](https://docs.lpeth.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lpeth.xyz/governance/voting-escrow.md). # Voting Escrow Participating in governance and earning bribes and other potential incentives, requires an account to have locked their liquidity pool tokens, lpETH. Users can choose a lockup between 1 week and 52 weeks, with improved rewards and more voting weight for longer lockups. \ \ Voting weight resulting from the locked "lpETH" is represented as "veLpETH". A non-transferrable ERC20 token of which the balance decays over time. VeTokens are both used for voting but also value-accrual, meaning the longer your remaining lockup the higher your voting weight but also the higher your share of any incentive pool. ### Dual Governance Once the governance token goes live, governance will be subject to dual governance, where both lpETH or the governance token can be used. --- # 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.lpeth.xyz/governance/voting-escrow.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.