My App
๐Ÿ“ Stake pool application

๐Ÿ“œ Validator application process

An overview of the application process for validators.

This page explains how to apply for approval and how applications are evaluated.

Apply for approval

You apply through a support ticket on Discord and an application form.

Open a support ticket

Open a support ticket and choose Validator.

In your ticket, use the /apply command. You receive a custom link to the application form.

Complete the form

Fill out the form. Applicants must provide accurate details, including validator performance, infrastructure details, and ecosystem contributions.

Request the Validators role

In your ticket, send staff your validator name, pubkey, and details about your validator, and ask for the Validators role.

After you apply

Your application goes through review and, if accepted, approval (Figure 6.1):

  • Review process: Submissions will be reviewed based on the minimum requirements and ecosystem contributions.
  • Approval: If accepted, validators will be placed on the approved list and given access to the Direct Stake Leaders and Elite Performance buckets. There is no waitlist.

Validator application flow: go to The Vault Discord, open a support ticket and choose Validator, use /apply for the custom form link, complete the form, request the Validators role, then enter review of minimum requirements, with the Validator Board voting on ecosystem contributions; if accepted, validators join the approved list, gain access to the Direct Stake Leaders and Elite Performance buckets, and there is no waitlist.

Figure 6.1: Validator application flow

Validator Board evaluation

The Validator Board is made up of validators from inside The Vault's stake pool who currently serve as board members. It votes on the ecosystem contributions of each applicant, using the Approved list criteria. Contributions include, but are not limited to:

  • Development of apps, tools, or infrastructure within Solana.
  • Active participation in Solanaโ€™s community.
  • Open-source development or meaningful contributions to Solana projects.

Evaluations are subjective and based on qualitative judgment.

Additional factors considered

  • Performance and uptime: Validators must meet minimum uptime and delinquency standards.
  • Vote credits and APY: Vote credits impact APY and are considered during evaluation.
  • Commission limits: Validators must adhere to commission guidelines. The Vault Contributors can make exceptions.

Acceptance terms

The Vault reserves the right to pause new additions to the approved list.

Compliance and ongoing requirements

  • Validators must maintain uptime, participate in governance, and contribute to the Solana ecosystem.
  • Failure to vote on SIMD proposals may result in removal from the approved list.
  • Validators that become delinquent, fail to meet base criteria, or lack contributions may be removed from the approved list.
  • Validators must settle Stake-as-a-Service fees in a timely manner. If an invoice stays unpaid for 20 epochs, the stakebot blocks delegation to your validator from the Direct Stake Leaders and Elite Performance buckets until your invoices are settled (Figure 6.2).

A Stake-as-a-Service invoice left unpaid for 20 epochs causes the stakebot to block delegation from the Direct Stake Leaders and Elite Performance buckets until the invoices are settled.

Figure 6.2: When an invoice stays unpaid

Grounds for removal or ban from The Vault

The Vault enforces strict governance to ensure fairness and security. Validators may be removed or banned from the stake pool for:

  • Failing to meet uptime or governance participation requirements.
  • Attempting to bribe, mislead, or exploit loopholes to gain access.
  • Participating in malicious activities that harm the network or the users of the network, for example, but not limited to, sandwich attacks.
  • Lacking community contributions after being approved.

Future updates

  • The Vault reserves the right to introduce new conditions or requirements.
  • Any changes to the approval process will be communicated in advance.
  • For detailed requirements, refer to the Stake pool delegation overview page.

On this page