# Nodes

### What Is a Node

A node is a key digital asset on hashed.farm that mines (generates) $HASH tokens when deployed to a datacenter. 

### Node Lifecycle

A node follows a clear lifecycle:

1. Built by selecting a tier and paying SOL
2. Deployed to a datacenter to begin mining
3. Deteriorates over time, reducing effective hashrate
4. Repaired or fused (upgraded) to maintain long-term value
5. Extracted to claim accumulated $HASH and redeploy to another datacenter for effectiveness.

{% hint style="warning" %}
Nodes that are **not** actively managed become less efficient over time.
{% endhint %}

### Node Tiers 

There are five tiers, each tier has 

* a randomized range of hashrate
* a chance to get a passive skill 

| **Node Tier** | **Build Cost (SOL)** | **Hashrate Range (MH/s)** | **Passive Skill Chance** |
| ------------- | -------------------- | ------------------------- | ------------------------ |
| Common        | 0.125                | 18–30                     | 25%                      |
| Uncommon      | 0.25                 | 40–65                     | 50%                      |
| Rare          | 0.5                  | 85–135                    | 75%                      |
| Ultra         | 1                    | 180–280                   | 100%                     |
| Superior      | 2                    | 370–590                   | 100%                     |

To build a node you need to have a corresponding amount of $SOL in your wallet. Make sure to deploy it to the datacenter, otherwise the node won’t generate the hashrate.

<br>


---

# 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.hashed.tech/core-concepts/nodes.md?ask=<question>
```

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.