> For the complete documentation index, see [llms.txt](https://docs.vetoken.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vetoken.finance/voting-and-gauge-weights.md). # Voting and Gauge Weights * Voting will be done via Snapshot * Gauge weight votes will be **bi-weekly,** starting Thursdays at 00:00 UTC and ending on Tuesdays 00:00 UTC. * Individual **xVE3D** holders may spread their votes among multiple pools in gauge weight votes. * Each gauge will have a hard cap of **50%** of **veToken's owned veAsset (veAngle, Dill, etc )** assigned to it. Overflow will be distributed to other pools in proportion to their vote weight. * Each gauge must receive at least **0.5%** of the votes before weight is assigned. * veAsset Project - veToken Team multi-sig is required to sign to establish outcomes of all veToken veAsset related votes. However, veToken Finance and partnered Asset project benefit each other, and proposals considered to be blatant attacks damaging either protocol will not be signed for. --- # 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.vetoken.finance/voting-and-gauge-weights.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.