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

Each subnet revolves around its subnet epoch based on its slot, and not the overall blockchain epoch.

Each subnet is assigned its own slot on activation, 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.

---

Why Epochs Slots?

Blockchains have computational limitations; therefore, to ensure the efficiency of the network for transactions and smart contracts, as well as for the scalability of increasing EVM execution, subnets and nodes, each subnet is assigned a slot (a block in an epoch). In each slot, logic specific to the subnet in the slot is run, such as distributing rewards, penalizing nodes, and electing the validator.