> 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/build-a-subnet-1/server.md).

# Server

The server class is the root from which all logic deploys.

If you are the subnet builder, it's important to ensure there is always a bootnode node available for other nodes to connect to. Hypertensor has [Overwatch Nodes](/overwatch-nodes/introduction.md), therefore not building a subnet that uses a Kademlia Distributed Hash Table will result in scores of 0 by them, rendering the subnet economically unviable. The most important element is the feature of ensuring each subnet is decentralized and proof of stake by ensuring they can connect to the subnet through a bootnode node. If you intend on building a centralized subnet, think again.

### Each Server class should:

{% hint style="warning" %}
See the Inference Subnet for a full example on how to use the Server class.
{% endhint %}

1. **Starts** or **joins the DHT**.
2. **Starts** the **heartbeat**.
3. **Deploys** and **starts** the **protocol** or [**protocols**](/build-a-subnet/protocols.md).
4. **Deploys** and **starts** the [**consensus mechanism**](/build-a-subnet/consensus.md) integrated with the [**scoring mechanism**](/build-a-subnet/consensus/scoring.md).