> For the complete documentation index, see [llms.txt](https://docs.hypertrend.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hypertrend.xyz/how-weve-aligned-our-teams-incentives.md).

# How We've Aligned Our Team's Incentives

HyperTrend has structured the team token allocations to unlock only when they make money for token holders.

Each 6 month period with a rolling Sharpe ratio of over 2.0 after fees, .0025% of team allocation is unlocked.

This means that if our trading vaults do not perform as well as the best hedge funds in the world, our team doesn't get anything.

Additional team tokens unlock based on total-value-locked (TVL) milestones we have set.

The more TVL, the more profit will be funneled to HyperTrend token holders.

* At 100m TVL, 1% of Team supply is unlocked
* At 200m TVL, 1% of Team supply is unlocked
* At 300m TVL, 1% of Team supply is unlocked
* At 400m TVL, 1% of Team supply is unlocked
* At 500m TVL, 1% of Team supply is unlocked

We have designed this structure to prevent the common scenario where teams cash out early regardless of protocol performance.

If you don’t make money, the team doesn’t get paid.


---

# 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.hypertrend.xyz/how-weve-aligned-our-teams-incentives.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.
