> For the complete documentation index, see [llms.txt](https://docs.hypertensor.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hypertensor.org/network/subnet/automatic-removal.md).

# Automatic Removal

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.

{% hint style="info" %}
Subnet reputation increases on each epoch that the subnet achieves a successful attestation.
{% endhint %}

### 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

{% hint style="info" %}
This scenario can only occur if the subnet is in the [enactment phase](/network/subnet.md#enactment-phase).
{% endhint %}

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**](/network/subnet.md#enactment-phase) for any reason, the subnet will be automatically removed.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hypertensor.org/network/subnet/automatic-removal.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.