Classifications
Classifications represent the lifecycle stages of a subnet node in the Hypertensor network. Each classification defines what a node is permitted to do or what must be accomplished to graduate—whether it's participating in consensus, earning emissions, or validating others. Nodes progress through these classifications over time, as each classification has a minimum length of epochs, and some classifications have goals that must be accomplished to graduate.
Each classification stage acts as a filter or checkpoint to prevent 66% takeovers, spam, sybil attacks, and gives subnets the ability to design ways to validate nodes are performing tasks and responsibilities before they can receive incentives (other than just assuming they are a node just because they are registered and submitting data on-chain), etc.
Registered
Trigger: Registration (extrinsic: register_subnet_node )
Subnet nodes that register in an active subnet will be registered as a Registered classified node.
Once registered, the node is added to the node queue (the queue to be activated).
Registered nodes are staked participants and are not included in the consensus; therefore, they do not receive emissions.
Idle
Trigger: Automated
On each epoch, nodes in the queue that have been queued for the length of epochs based on the SubnetNodeQueueEpochs will be activated and updated to the Idle class. The number of nodes that are activated is based on the subnet's churn limit, up to the maximum nodes allowable per subnet.
Included
Trigger: Automated
Nodes are upgraded to Included once they are in the Idle class and have been in this class for the length of the IdleClassificationEpochs epochs and have zero penalties.
Included-classified subnet nodes are required to be included in consensus; otherwise, they will increase their node penalties (and can be removed if they surpass the maximum allowable penalties the subnet sets). For each epoch included in the consensus, penalties will be decreased by one.
Validator
Trigger: Automated
Nodes are upgraded to the Validator class once they are in the Included class, and are consecutively included in consensus data that is in consensus for the length of the IncludedClassificationEpochs, and have zero penalties.
Validator classified nodes can:
Be elected subnet validator node
Attest consensus data
Receive emissions
Last updated