> For the complete documentation index, see [llms.txt](https://docs.hyperbeat.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperbeat.org/hyperbeat-staking/behype/validator-set.md).

# Validator set

The beHYPE validator set is made up of all **active set** validators **excluding** the Hyperliquid Foundation nodes. 

{% @arcade/embed flowId="mFexuU8yB1uzFG4UeaT8" url="<https://app.arcade.software/share/mFexuU8yB1uzFG4UeaT8>" %}

{% hint style="success" %}
[View the beHYPE validator set here](https://app.hyperbeat.org/staking)
{% endhint %}

All validators in the beHYPE validator set are continuously audited to monitor, performance, reliability, engagement and more. If any community validator does not hit the benchmarks they will be removed from the beHYPE set with stake redistributed equally amongst the remaining validators in the set.

## How is stake split between validators in the set?&#x20;

beHYPE uses CoreWriter for stake delegation to delegate HYPE equally amongst all community validators in the beHYPE active set by default.&#x20;

## How often is stake rebalanced?

Delegations are rebalanced every 6-hours.&#x20;


---

# 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.hyperbeat.org/hyperbeat-staking/behype/validator-set.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.