> For the complete documentation index, see [llms.txt](https://delegates.iotex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://delegates.iotex.io/introduction/hardware-specs.md).

# Hardware Specs

{% hint style="info" %}
Adhering to minimum technical standards is crucial. Failing to meet these can affect the entire network performance and lead your Delegate node being probed for six blockchain epochs without reward, if it's unable to generate blocks on time.
{% endhint %}

### **Recommended Hardware Specifications**

For optimal performance, especially during high blockchain traffic, consider the following recommended setup. This ensures reliability and efficiency for your delegate infrastructure, particularly if you aim to be a consistent block producer.

<table><thead><tr><th width="96">RAM</th><th width="178">STORAGE SPACE</th><th>DISK</th><th width="204">CPU</th><th>NETWORK</th></tr></thead><tbody><tr><td>64 GB</td><td>500 GB</td><td>SSD or Nvme</td><td>8 Cores, 2.4 Ghz, 64 bit</td><td>1 Gbit</td></tr></tbody></table>

{% hint style="info" %}
**Backup Node:** Implement at least one backup node for software updates and maintenance.
{% endhint %}

### **Software and Operational Guidelines**

<table><thead><tr><th width="219">OS</th><th width="200">Compilers</th><th>Tools</th><th>Software</th></tr></thead><tbody><tr><td>Debian Stretch Linux</td><td>Go-Lang > 1.18.5</td><td>Monitoring &#x26; Alerting</td><td>Docker</td></tr></tbody></table>

* Maintain 99.99% server uptime.
* Implement failover and data backup across different geolocations.
* Prioritize security with preventive measures.
* Regularly support and update node software.

### Redundancy and Security

A primary server with one or more backup servers, all secured behind a firewall, is advised. This configuration aids in uninterrupted operation during software upgrades.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://delegates.iotex.io/introduction/hardware-specs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.