# Epochs & Slots The blockchain has epochs, but there are also subnet epochs. ### Blockchain Epochs The blockchain has epochs where business and accounting logic runs to manage subnets and nodes. On the **first block** of each epoch, blockchain validators will see if any subnets need to be removed. Subnets will be removed from the blockchain if they do not have the minimum required delegate stake balance or do not have the minimum required number of nodes. On the **second block** of each epoch, blockchain validators will compile subnet weights for the distribution of rewards. These weights are based on the subnet delegate stake weight of each subnet. ### Subnet Epochs & Slots Each subnet revolves around its **subnet epoch** based on its **slot**, and not the overall general blockchain epoch. Each subnet is assigned its own slot on activationâžșa block in an epoch, where rewards are distributed and the validator is elected. To ensure each subnet gets the full epoch length for consensus, subnet epochs overlap with the blockchain's epoch. If the blockchain is on epoch 2, a subnet may still be on epoch 1, depending on its assigned slot. --- # Agent Instructions: 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: ``` GET https://docs.hypertensor.org/network/epochs-and-slots.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.