# Validators

## Validator Selection

To reduce the risk impact of validator operations, and to increase decentralization, the TruYields Protocol partners with a small number of node operators, selectively chosen based on the following criteria:

* **Validator performance** – At TruYields, we assess partners based on their performance across key metrics such as: Uptime, Checkpoints signer, APR, and Delegated Stake.
* **Information security** – Given the institutional focus of TruYields, node operators and their implementation of information security measures are a core part of the validator partner selection process. This ensures that our chosen partners are security-focused and aligned with the enterprise-grade security of the TruYields Protocol itself.
* **AML/KYC requirements** – Although users can delegate their native assets to available network validators, TruYields works with partners who implement strict AML/KYC requirements during the onboarding process of their clients, ensuring funds are not pooled on the same validator as non-KYC’d non-AML’d wallets.

## Onboarding Validator Phases

During an onboarding phase, validators must complete a three-step process:

1. Ensure they meet TruYields's requirements
2. Apply to join the **Allow List**
3. Maintain performance requirements

### 1. Ensure that your validator meets TruYields's requirements[​](https://docs.drop.money/validators/onboard#1-ensure-that-your-validator-meets-drops-requirements) <a href="#id-1-ensure-that-your-validator-meets-drops-requirements" id="id-1-ensure-that-your-validator-meets-drops-requirements"></a>

To be eligible for protocol delegations, validators must continue to meet the following requirements:

* Operate their own infrastructure
* Have commissions set between 5% and 10% included
* Maintain >95% uptime over the last 90 days period
* Avoid jailing, slashing or tombstoning

### 2. Apply to join the **Allow List** during an Onboarding Phase[​](https://docs.drop.money/validators/onboard#2-apply-to-join-the-allow-list-during-an-onboarding-wave) <a href="#id-2-apply-to-join-the-allow-list-during-an-onboarding-wave" id="id-2-apply-to-join-the-allow-list-during-an-onboarding-wave"></a>

> 💡 As part of the onboarding process, TruYields may request information considered sensitive by your organization. Please only share what you are able to, and note that any information shared in this process will be kept confidential by TruYields.

To apply, validators should reach out to <onboarding@truyields.com> to receive an onboarding questionnaire.

TruYields contributors will review your application and confirm your eligibility to the protocol’s **Allow List** based on the aforementioned requirements.

If you’ve missed the first onboarding phase, make sure to follow [@TruYields](https://x.com/TruYields) on X to be notified of future onboarding phase openings.

### 3. Maintain performance requirements[​](https://docs.drop.money/validators/onboard#3-maintain-performance-requirements) <a href="#id-3-maintain-performance-requirements" id="id-3-maintain-performance-requirements"></a>

Once onboarded to the **Allow List**, your validator will be eligible to receive protocol delegations from TruYields. As the protocol grows, the number of delegation slots may increase.

To remain in the **Allow List**, your validator will be expected to maintain a high degree of reliability and performance:

* Maintain >95% uptime,
* Maintain a commission rate between 5% and 10% included
* Avoid jailing, slashing or tombstoning

Operators that fail to maintain high uptime, or are slashed, jailed or tombstoned will be removed from the **Allow List**. They can re-apply at the next onboarding phase, once underperformance has been resolved.


---

# Agent Instructions: 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://truyields.gitbook.io/docs/trustake-vaults/validator-selection.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.
