Handling Max Nodes

In the scenario where a subnet has the maximum number of nodes, multiple systems are in place for subnets to utilize.

Note

The maximum node removal system is set by the subnet owner.

Consensus and Manual

When the subnet is full, utilizing this option, the only way to enable activating nodes in the registration queue is by removing currently active nodes through consensus or done through the subnet owner.

Since nodes are queued, this option has little control over which node is able to activate.

Stake System

When the subnet is full, utilizing the Stake Precedence model, nodes can activate and remove the node with the least stake, with time in the subnet being the tie-breaking factor, as long as the activating node has a higher stake balance.

The subnet can utilize the NodeRemovalStakePercentageDelta which requires a percentage delta between the activating node and the potential removing node. For example, if the percentage delta is 10% and the activating node has a stake of 1000, the potential removing node must have a stake of less than 900.

Reputation System

Using the reputation model, the activating node will remove the node with the lowest coldkey reputation, as long as the activating node has a higher colkey reputation.