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

# mSHERP

At the heart of the Sherpa trading protocol is the `mSHERP` lockup mechanism. With this, users stake `SHERP` for a predetermined amount of time, receiving in return the yield bearing `mSHERP`.

### Core Components <a href="#core-components" id="core-components"></a>

The `mSHERP` system takes its core components from the longstanding and sustainable `veCRV` and `vePENDLE` systems, with the following changes unique to Sherpa:

* `mSHERP` offers a volume multiplier
* `mSherp` holders receive numerous protocol specific benefits based on the amount of time locked and stake value committed, including
  1. Strategy creation rights
  2. Voting weight and fee intake percentages
* mSherp holding tiers are intentionally configured to incentivize large individual holders over sybils.

### Supply and Value <a href="#supply-and-value" id="supply-and-value"></a>

`mSHERP` is transferable but the protocol will not add, maintain, or incorporate any liquidity relating to `mSHERP` into its framework; only `SHERP` is liquid. Its value will therefore be directly determined by `SHERP`. The maximum possible supply of `mSHERP` is 20B tokens. This is exactly two times the total supply of `SHERP`. Although possible, there is a near zero chance this amount of mSHERP will even be minted based on the game theory regarding its [conversion factors](https://docs.sherpa.trade/docs/conversion-factors).

<figure><img src="/files/Dm3BGuQPtdiOxkHczIqn" alt=""><figcaption></figcaption></figure>


---

# 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.sherpa.trade/general/tokenomics/msherp.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.