Automatic Removal

Subnet removal and reputation

The following is a list of automatic subnet removal conditions that can occur on each epoch step.

Active Subnets

Minimum Reputation

If the subnet's reputation goes below the minimum reputation of 10%, the subnet is removed. This is checked on each epoch step.

Reputation decreases under the following conditions:

• The subnet is paused and has passed the maximum allowable pause epochs.

• The subnet has fewer nodes than the required minimum.

• The subnet attestation ratio is below 66%.

• The elected validator fails to submit consensus data.

Subnet reputation increases on each epoch that the subnet achieves a successful attestation.

Minimum Delegate Stake Balance

If the subnet's minimum delegate stake balance is below the subnet's minimum required delegate stake balance, the subnet is removed.

Maximum Subnets

The network allows max+1 subnets in the network to ensure subnets are constantly in competition. Subnets can register and activate if the maximum number of subnets is already present, meaning there is always one excess slot available.

Every 10 epochs, if the maximum number of subnets threshold is exceeded, the network will remove the lowest-performing subnet based on the delegate stake balance to ensure that all active subnets are high-performing.

---

Registered Subnets

Minimum Subnet Validator Nodes

This scenario can only occur if the subnet is in the enactment phase.

If the subnet has fewer nodes than the required minimum.

Past Enactment Period

If the subnet owner fails to activate the subnet beyond the enactment phase for any reason, the subnet will be automatically removed.