> For the complete documentation index, see [llms.txt](https://docs.x1.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.x1.xyz/validating/performance/hardware-requirements.md).

# Hardware requirements

### Minimum XNT requirements[​](https://docs.solanalabs.com/operations/requirements#minimum-sol-requirements) <a href="#minimum-sol-requirements" id="minimum-sol-requirements"></a>

There is no strict minimum amount of XNT required to run a validator on X1.

### Hardware Recommendations <a href="#hardware-recommendations" id="hardware-recommendations"></a>

The hardware recommendations below are provided as a guide. Operators are encouraged to do their own performance testing.

* CPU
  * 12 cores / 24 threads, or more
  * 3GHz base clock speed, or faster
* RAM
  * 192GB or more
* DISK
  * 4TB NVME

Server needs to be bare metal dedicated, not VPS.

Example: <https://www.interserver.net/dedicated/amd-ryzen-7900x>

{% hint style="info" %}
Hardware specifications can and most likely will change over time. Server costs will increase as the chain gets more adoption.
{% endhint %}


---

# 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.x1.xyz/validating/performance/hardware-requirements.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.