> For the complete documentation index, see [llms.txt](https://docs.hyperhive.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperhive.finance/the-usdhive-token/usdhive-utility.md).

# $HIVE Utility

HIVE serves a protocol that manages capital on behalf of its users, so its utility centers on the decisions that affect that capital:

**Revenue share** — staking HIVE for a share of protocol performance fees, live before the liquidity event.

**Governance** — strategy whitelisting, allocation caps, risk parameters, vault multipliers, and fee levels.

**Fee direction** — voting on how protocol revenue splits between stakers, treasury, and buybacks.

**Access** — priority allocation into capacity-constrained strategies and new vaults at launch.

**Liquidity incentives** — directing emissions toward the pools the protocol needs to be deep.

Every one of these points at the same thing: keeping the token and the protocol growing together over the long run. HIVE holders decide how capital is deployed and how revenue is split, and what the token is worth tracks how much capital the protocol manages — so the incentive to build it out sits with the people who own it.

<br>


---

# 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.hyperhive.finance/the-usdhive-token/usdhive-utility.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.