> For the complete documentation index, see [llms.txt](https://docs.creditcoin.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.creditcoin.org/cc-enterprise/validator-guides/minimum-requirements.md).
# Minimum Requirements
The most common way for a beginner to run a validator is on a cloud server running Linux. We strongly recommend using a recent Debian Linux OS. For this guide we will be using **Ubuntu 22.04**, but the instructions should be similar for other platforms.
{% hint style="danger" %}
Creditcoin does not currently support Macs using Apple silicon, such as the M1 and M2
{% endhint %}
* **CPU**
* Intel Core i5-8400 or better
* 6 Cores @ 2.8Ghz
* 9M Cache
* **Storage**
* Needs to be sufficient for targeted chain
* **Memory**
* 8GB
* **System**
* Ubuntu 22.04 (Linux Kernel 5.16 or newer)
* **Tokens**
* The minimum stake required to run a validator is currently 1000 CTC
> 
>
> It is strongly recommended that validators either meet or exceed these hardware specifications in order to ensure that they can process all blocks in time. If you use subpar hardware you will possibly run into performance issues, get less era points, and potentially even get slashed.
The transaction weights in Creditcoin are benchmarked on reference hardware. We ran the benchmark on a memory optimized `Standard_E4as_v4` VM instance of Azure.
---
# 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.creditcoin.org/cc-enterprise/validator-guides/minimum-requirements.md?ask=&goal=
```
`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.