Selendra
EXPLORER
Blog / Roadmap

2025 Roadmap: Expanding the Validator Set

Roadmap2025-01-20·5 min read·By Selendra Team

For the past three years, the Selendra validator set has been relatively static. This was a conscious choice to ensure stability while we learned how to operate the network.

Now, as we enter 2025, we are following the path laid out by many successful networks before us. We are transitioning to Phase 2: The Reserved Validator Set.

Why "Reserved"?

We are adopting a Proof of Stake Authority (PoSA) model. This is a well-understood mechanism used by various chains to balance decentralization with performance.

In this phase, we are opening slots to qualified partners who can demonstrate the technical capability to run high-performance nodes.

Technical Requirements

To ensure the network remains healthy, we are aligning our requirements with industry standards for high-throughput chains:

Hardware

  • CPU: 4+ cores (Modern architecture recommended)
  • RAM: 16GB DDR4 ECC (32GB preferred)
  • Storage: 500GB NVMe SSD (Essential for 1s block times)
  • Network: 1Gbps symmetric connection

Staking

  • Minimum Bond: 25,000 SEL
  • Self-Stake: Validators must self-stake at least 50% of the minimum bond.

Note: The bond requirement was updated via governance vote #42 to align with the network's economic security needs.

The Onboarding Process

We are using the standard pallet-staking and pallet-session mechanisms provided by Substrate:

  1. Application: Submit a metadata hash of your validator setup.
  2. Testnet Trial: Validate on the Indra testnet to prove stability.
  3. Key Submission: Submit SessionKeys (Aura + AlephBFT).
  4. Governance Vote: The Technical Committee will verify performance and vote to include the keys.

Why This Approach?

We are not reinventing the wheel. We are simply applying best practices to prevent "validator churn" and ensure that our 1-second block time—a feature enabled by the underlying consensus engine—remains stable.

Timeline

  • Q1 2025: Onboard first batch of external validators.
  • Q2 2025: Monitor consensus performance.
  • Q3 2025: Evaluate further expansion.

If you are ready to run a node, check the Run Validator documentation.