> 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/terminology.md).

# Terminology

### Terminology 

veAsset Projects - *Projects Token use voting escrow token economics. Project has a token (we call this "Asset"). Users can lock up their Asset for a period and they receive "veAsset" (the longer the lock, the more veAsset is received )*\[1]

Gauges - *Gauge weighting is the {total amount of veAsset voting for the gauge} / {total amount of veAsset }. The rewarded Asset per Vault is calculated based on "Gauge weighting", which displays the current gauge weighting as well as the pending gauge weighting, and shows current reward ratio and pending reward ratio per vault* \[1]

VE3D- Governance token that issued by veToken Finance 

veAsset - Token that adopted veModel ( Pickle, Angle, CRV, etc)

ve3Token - - Tokenmized veAsset token created by veToken finance

ve3CRV - Tokenmized veCRV token created by veToken finance

ve3DILL - Tokenized Dill created by veToken Finance

## Reference<br>

\[1] reference: <https://github.com/antonnell/veToken-voting>

\[2] Gemini: <https://www.gemini.com/cryptopedia/decentralized-autonomous-organization-dao#section-da-os-a-solution-to-the-principal-agent-dilemma>


---

# 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/terminology.md?ask=<question>&goal=<endgoal>
```

`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.