> For the complete documentation index, see [llms.txt](https://docs.campiexyz.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.campiexyz.io/reference/glossary.md).

# Glossary

## **GRAIL**

Grail  serves as the native token of Camelot.

## **xGRAIL**

xGRAIL is a non-transferable escrowed governance token that corresponds to staked GRAIL. It can be earned through yield-generating staking positions (spNFTs) or by converting GRAIL directly. The primary purpose of xGRAIL is its allocation to Plugins. This process involves staking xGRAIL into the token contract and assigning the deposited amount to a plugin in exchange for various benefits.

## **Camelot DEX Plugins** <a href="#id-4466" id="id-4466"></a>

* Dividends: xGRAIL holders get active user engagement rewards from the Camelot platform.
* Launchpad: GRAIL holders receive access to the launch of new tokens within Camelot.
* Yield Booster: Liquidity Providers can enhance their rewards by allocating xGRAIL through this plugins.
* Gauges: (Work In Progress)

## **mGRAIL**

mGRAIL refers to "Magpie GRAIL", is a liquid version of xGRAIL that allows users to earn rewards for their active participation on Campie. GRAIL holders can convert tokens into mGRAIL on Campie to earn boosted APR without having to lock their assets.

## **CMP**

CMP is the governance and active user engagement rewards token of Campie.

## **vlCMP**

Vote-Locked CMP is the locked version of CMP. vlCMP holders control the voting power that Campie wields on Camelot DEX. Users can lock their CMP to obtain vlCMP at a 1:1 ratio. vlCMP holders are entitled to a part of the active user engagement rewards and also have governance rights. Vote-Locked CMP holders can participate in the governance of both Camelot DEX and Campie.


---

# 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:

```
GET https://docs.campiexyz.io/reference/glossary.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
