Skip to main content

Validators

SphereNet validators operate under a Proof of Governed Stake (PoGS) consensus mechanism. While any node can operate as a validator, only whitelisted validators can receive stake delegations, effectively limiting voting power to approved validators. The validator whitelist is maintained via on-chain governance and stored in a dedicated account.

Each whitelisted validator entry tracks:

  • An identity public key identifying the validator
  • A start epoch indicating when the validator start receiving stake delegations
  • An end epoch indicating when the validator's authorization expires

Onboarding Process​

1. Application​

To become a validator, candidates must submit a governance proposal containing their validator identity public key and requested start and end epochs. The proposal should include a link to off-chain documentation detailing technical infrastructure, operational procedures, compliance certifications, and KYC/AML verification proof.

CORE holders are responsible for voting to add validators to the whitelist. Validators can request consecutive whitelist terms by submitting a new governance proposal before their current term expires. There is no limit on the number of consecutive terms a validator can remain whitelisted if approved by governance.

2. Review Period​

During the review period, CORE holders examine validator credentials while the technical committee assesses infrastructure requirements. This period includes compliance verification and performance testing to ensure the validator meets all necessary standards.

3. Voting​

CORE holders vote on the validator proposal. Upon approval, the governance program automatically adds the validator to the whitelist and sets the requested start and end epochs for their term.

4. Activation​

When the start epoch is reached, the validator becomes eligible for the leader schedule and their performance metrics begin being tracked.

Performance Requirements​

Validators must maintain (for example purposes):

  • Minimum 98% vote participation
  • Maximum 1% missed leader slots
  • 99.9% uptime
  • Response to network upgrades within specified timeframes
  • Secure key management practices

Removal Process​

A validator can be removed from the whitelist before their term ends through governance voting. This process requires a formal governance proposal, which can be submitted by any CORE holder, including the validator themselves. The proposal must include substantial evidence or rationale for early termination, such as documented poor performance, security incidents, compliance violations, or a voluntary exit request from the validator.

Due to the critical nature of validator changes, these proposals require both a higher quorum and approval threshold compared to standard governance votes. Once approved, the removal takes effect immediately.

Note: All changes to validator status, including early termination, must go through governance voting with higher thresholds than standard proposals to ensure network stability.