# Technical Requirements

## **Setup and Hardware**

Validators can choose to run their systems in the cloud or in a dedicated data center. It needs to be pointed out that if running your validators in the cloud you are risking exposure of your private keys.&#x20;

There is a spectrum of different choices that can be made in the name of security. The most secure is a complex arrangement where the validator sits in a data center with some sort of KMS hardware key management system and has one or more sentries sitting in the cloud, with an elaborate setup of private VPN’s and firewalls.

### **Validator and Sentry Node Requirements**

Bluzelle requires validators to have both a validator node and sentry node.&#x20;

| Validator Node                                                                                                             | Sentry Node                                                                                                                        |
| -------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| <ul><li>I3EN Large</li><li>16 GB RAM</li><li>2 vCPU’s</li><li>25 Gigabit Network Connection</li><li>1 TB Storage</li></ul> | <ul><li>M5AD Extra Large</li><li>16 GB RAM</li><li>4 vCPU’s</li><li>10 Gigabit Network Connection</li><li>125 GB Storage</li></ul> |


---

# 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.bluzelle.com/developers/staking/validator/technical-requirements.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.
