> ## Documentation Index
> Fetch the complete documentation index at: https://docs.yield.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Preferred validators

> Fetch Yield.xyz's curated, pre-vetted validators for a staking yield, filter to them with the preferred flag, and run a whitelabel validator under your own brand.

The Preferred Validator Network (PVN) is a registry of validators that Yield.xyz curates and maintains centrally, across the networks where a staking yield supports choosing a validator. Preferred status is a property of the validator itself, set by Yield.xyz; it is not something an integrator configures per project.

## When it applies

Preferred validators exist only for staking yields where you select a validator on enter (`mechanics.requiresValidatorSelection: true` on the yield object). For those yields, `GET /v1/yields/{yieldId}/validators` returns every validator Yield.xyz indexes for that yield, each with a `preferred` boolean. Filter to `preferred=true` to return only PVN members.

> [!NOTE]
>
> PVN validators are selected on historical uptime, performance, total value staked, and slashing history, and operate under SLAs covering uptime and slashing protection.

## Fetching preferred validators

Call `GET /v1/yields/{yieldId}/validators?preferred=true` for the yield you want to stake, for example `solana-sol-native-multivalidator-staking`. The endpoint also accepts `name`, `address`, `provider`, and `status` filters, plus `offset` and `limit` for pagination. There is no endpoint for browsing preferred validators across yields; query each yield's validators individually.

The fields you need to choose a validator:

* `address`: the value you pass as `validatorAddress` (or in `validatorAddresses`).
* `preferred`: `true` for validators Yield.xyz flags as preferred.
* `commission`: the validator's commission, as a decimal.
* `status`: `active`, `jailed`, `deactivating`, `inactive`, `full`, or `not_found`.

For the full validator object, see the [validators endpoint reference](/api-reference/YieldsController_getYieldValidators.md).

## How it fits the staking flow

When a staking yield requires validator selection, fetch its validators before calling enter. Filtering to `preferred=true` narrows that list to PVN members so you can default users to a vetted set instead of surfacing every indexed validator. The selected validator's `address` is then passed as `validatorAddress` (or one address per entry in `validatorAddresses` for yields that support splitting a delegation) in the enter request.

## Whitelabel validators

If you want a validator under your own brand without running infrastructure, Yield.xyz can deploy and operate a dedicated validator for you, under a name and identity you choose. You set the commission and capture the rewards the node earns; Yield.xyz handles deployment, monitoring and node operations. Delegations reach it the same way as any other validator: discover it on the yield's validators endpoint and pass its `address` as `validatorAddress`.

Whitelabel validators are arranged directly with Yield.xyz, with no self-serve dashboard or API flow, and are available on the Pro and Enterprise [plans](/documentation/plans-limits/plans-tiers.md). They can be scoped for the proof-of-stake networks below; confirm current availability for a network before committing to a deployment.

> **Networks and tokens**
>
> | Token | Network |
> | - | - |
> | ETH | Ethereum |
> | SOL | Solana |
> | AVAX | Avalanche |
> | ADA | Cardano |
> | DOT | Polkadot |
> | NEAR | Near |
> | TRX | Tron |
> | POL | Polygon |
> | BNB | BNB Chain |
> | CELO | Celo |
> | ONE | Harmony |
> | XTZ | Tezos |
> | ATOM | Cosmos Hub |
> | CRO | Crypto.org Chain |
> | OSMO | Osmosis |
> | INJ | Injective |
> | SEI | Sei |
> | DYDX | dYdX |
> | AKT | Akash |
> | KAVA | Kava |
> | AXL | Axelar |
> | FET | Fetch.ai |
> | XPRT | Persistence |
> | CORE | Coreum |
> | MANTRA | Mantra |
> | BAND | Band Protocol |
> | IRIS | IRISnet |
> | SOMM | Sommelier |
> | BLD | Agoric |
> | STARS | Stargaze |
> | JUNO | Juno |
> | QCK | Quicksilver |
> | UMEE | Umee |
> | XKI | Ki Network |
> | GRAVITON | Gravity Bridge |
> | REGEN | Regen |
> | NOM | Onomy |
> | CRE | Crescent |
> | DVPN | Sentinel |
> | CMDX | Comdex |
> | HUAHUA | Chihuahua |
> | TORI | Teritori |
> | DSM | Desmos |
> | BTSG | BitSong |

> [!NOTE]
>
> Active-set minimums, self-delegation requirements and validator counts vary by network and move with market conditions. Yield.xyz confirms current requirements when scoping a deployment. To start, [contact us](mailto:hello@yield.xyz).

## Next steps

> **[Bring your own node](/documentation/earn/staking/validators/bring-your-own-node.md)**
>
> Route delegations through validators you already operate instead.

> **[Actions](/documentation/earn/core-concepts/actions.md)**
>
> Pass a validator address when entering a staking yield.

> **[Validator selection guide](/guides/earn/staking/validator-selection.md)**
>
> Fetch validators and choose one before you enter, step by step.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.