Skip to content

Latest commit

 

History

History
95 lines (84 loc) · 5.72 KB

README.md

File metadata and controls

95 lines (84 loc) · 5.72 KB
Raw

1KV Nomination Tool

This repository is dedicated to the development of a tool to help nominate validators from the Thousand Validator Programme. The selection criteria and frequency can be specified via a settings file (Settings.ts). Should this tool be used by a Parachain, it is envisaged that the parameters can be integrated into its chainstate and loaded (into this application) upon start up.

How does it work?

The system is designed around three (3) sources of validators.

  1. Partners - These validators are always selected providing that they are nominable*.
  2. Preferred Validators - This is a list of validators that are chosen manually and specified in Settings. The system relies on them in the event that there aren't sufficient candidates in the subsequent list (3).
  3. Thousand Validator Candidates - These validators are automatically retrieved from the thousand validator system. These candidates must:
    1. Have no faults
    2. Issued all pending payouts
    3. Not part of the active set at time of the check
    4. Commission is within the range as specified in Settings

Validators in referenced lists two (2) and three (3) are all merged together into a single list. The candidates therein will then be subjected to tests each of which provides a weighted score. These tests are:

  • Self Stake - Self stake is a visible and shared risk demonstrated by the validator. The system prefers validators with higher self-stake and encourages validators to compete to increase their stake. As-to not overly skew comparisons, a setting is provided to help remove outliers.
  • Eras validated - Validators should demonstrate some history of validation relative to the period of analysis. The system prefers validators with more active validation to a limit set in Settings
  • Commission - Validators should provide commissions within reasonable ranges. Those who present commissions on towards the lower boundary of the range would receive a higher score.
  • Era Points - Era points are the basis from which rewards are calculated, the system prefers validators with high average scores over an analysis period. Granted that era_points are generated with a degree of randomness it is anticipated that all validators should have similar scores over time. Under normal conditions this would not influence comparitive weighting. However, in the exceptional case that a validator is not configured properly his era points would be below mean and thus lose some of this score.
  • Nominated Stake - The system prefers a validator set with a normalized stake. This rewards validators who attempt to attain nominations independently but also protects the nominator against nominating validators with too many nominations.
The boundaries of some tests, and the weights for each test, is configurable in the settings file.

With a sorted list of weighted candidates attained, nominable* validators would be selected based on highest score, this resultant list is referred to as the winners. If any nominable validator exceed the nominated stake threshold or has too many instances already nominated they'll be put into a runner's up list. These threshold and limits are all configurable in the settings.

Lists are now created for Partners, Winners and Runner's up. The system merges the final list as follows:

  1. Nominable Partners are placed first
  2. Winners are placed next up to the maximum number of nominations
  3. If the above two don't meet the maximum number of nominations, then the remaining are taken from the runner's up list

Nominable - Validators should have the validator intent and not have their nominations blocked. If nominations are blocked validators the nominate extrinsic will fail

Goal

It is with great hope that liquid KSM/DOT providers utilize this platform or components thereof to help elect reliable, independant and profitable validators to help further decentralize the active set (by entity).

Installation

The application relies on installation of ts-node, node-fetch@2, ts-log and @polkadot/api. Once these are installed you may execute using the command

ts-node app.ts

You will need to configure a private file with a seed phrase, a deriviation path and a ws/wss server in JSON format. A sample file is provided named hidden_file.sample. If the account has no deriviation path then use -1. It is highly recommended that you use a proxy account for this operation which only has access to switch nominations.

It is recommended that the application is run under systemd.

Future Development

  • Output of nominations to a Matrix channel along with their scores as an archive and for audits.

Promotion

If you like this tool and would like to lend support to the developer kindly consider nominating my validator nodes

Polkadot

  • PARANODES.IO/01 - 14hM4oLJCK6wtS7gNfwTDhthRjy5QJ1t3NAcoPjEepo9AH67

Kusama

  • PARANODES.IO/01 - H3DL157HL7DkvV2kXocanmKaGXNyQphUDVW33Fnfk8KNhsv
  • PARANODES.IO/02 - HtYny8Eker9VBEKQrtBd6Y5PTkaHQFSvyMFy2bkd66wGBan
  • PARANODES.IO/03 - FkWky3r2bryP3aaAwVWykYrKesAwkDyKZWsDyBvck7YawSi
  • PARANODES.IO/04 - EsNZHmG4bQMGzQNK4Z2CR7Hdhu4or7p2vsLRChUEJcjJAeU
  • PARANODES.IO/05 - EriYFJuqCeBF6SFkKxyQWwaTvT9tcoF9ZGDQ4LX3a1iBsYr

Primary Identity

  • Paradox - HqRcfhH8VXMhuCk5JXe28WMgDDuW9MVDVNofe1nnTcefVZn