> For the complete documentation index, see [llms.txt](https://docs.hashed.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hashed.tech/core-concepts/datacenters.md).

# Datacenters

### Overview

After you’ve built a node, it needs to be put[^1] to the datacenter in order to start mining $HASH.

### Available Datacenters

* **Neon Haven**
* **Phoenix Foundry**
* **Shadow Mines**
* **Void Hive**

Each datacenter distributes 1% of its current $HASH pool, unless affected by Datacenter Events. 

The rewards are distributed at randomized periods to avoid abuse.

You can move nodes between datacenters by extracting a node and rewards, but timing and strategy matter.

**It is important to check the specs of the datacenter when deploying a node.** 

You’ll see capacity, available $HASH to mine in the pool and cumulative hashrate. 

| Spe                 | What It Means            | Why It Matters                    |
| ------------------- | ------------------------ | --------------------------------- |
| Capacity            | Max nodes that can mine  | Limits competition                |
| Pool                | Total $HASH available    | Bigger pool = bigger rewards      |
| Cumulative Hashrate | Total MH in pool         | More power means more competition |
| $HASH / MH          | Reward per unit of power | Shows efficiency                  |

<br>

[^1]: deployed


---

# 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.hashed.tech/core-concepts/datacenters.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.