# Validators

## How Pye Benefits Validators

Validators on Solana compete on thin margins with little differentiation. Commissions are public, rewards are commoditized, and most stakers have no reason to choose one validator over another.

By using Pye, validators gain tools to attract stake, retain stakers, and generate additional revenue — without changing how they operate.

***

## Getting Listed

Validators must register with Pye before integrating the Rewards Widget or appearing on the platform. Registration gives you access to all Pye features: widget listing, markets on the Pye exchange, widget embed, and the Custom Commission CLI.

Once approved, your validator appears in the Pye exchange and widget. Stakers with active stake accounts can interact with your validator via the Rewards Widget.

[Apply to be listed →](https://pye.fi)

***

## Fixed Deposits and Predictable Revenue

When a staker sells their future rewards on Pye, their SOL remains locked with your validator until the maturity date. This means:

* **Stable & new revenue** — locked positions generate consistent staking rewards for the duration of the maturity period. Whenever your staker uses the Pye Widget to sell their future rewards, a fee goes to you, manageable from the Validator Dashboard.
* **Predictable withdrawal schedules** — stake delegated through Pye follows fixed quarterly maturities, so you know when redemptions will occur
* **Reduced churn** — stakers who have transacted through Pye are committed to the maturity date, reducing unstaking until the maturity date.
* **Trading Fees** — validators who integrate with the widget can earn additional fees without breaking the user experience.

***

## Validator FAQ

<details>

<summary>Do my existing stakers need to do anything?</summary>

No. Stakers with existing positions can use Pye directly — the program detects existing stake accounts when using Pye Trade or the Rewards Widget without requiring deactivation. There's nothing you need to change on your end. Once you're listed, your validator appears in the marketplace automatically.

</details>

<details>

<summary>Does Pye change how my validator operates?</summary>

No. Pye sits on top of your existing operation. You continue to run your validator as normal. Pye handles the orderbook, token minting, and staker experience. The Programmable Stake Accounts (PSA) operate like a wrapper around the native solana stake accounts and stake is confined to specific lockups, delegated back to you. The PSA has mint and withdraw authority.

</details>

<details>

<summary>What happens at maturity?</summary>

Stakers who deposited through Pye can redeem their Principal tokens or Reward tokens on Pye at the end of the quarter. The underlying stake may be withdrawn or rolled over depending on the staker's choice. Withdrawals follow Solana's standard cooldown period.

</details>

<details>

<summary>Is the widget free?</summary>

Yes. The Rewards Widget is free for all whitelisted validators. Revenue flows through orderbook trading fees, not validator charges.

</details>

<details>

<summary>Can I offer different terms to different stakers?</summary>

Yes, via the Pye CLI. You can offer custom commission structures to specific stakers outside of your public on-chain commission.

</details>

<details>

<summary>Am I offering these lockups or are stakers opting in?</summary>

Stakers opt into lockups based on pre-defined periods. When a staker engages with a specific validator via Pye, the underlying stake is locked with that validator until maturity. The responsibility lies with the staker who is partaking in the action.

</details>


---

# 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://docs.pye.fi/validators.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.