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

# Introduction

Welcome! This guide will walk you through setting up your BLOCX Validator Node using the official [BLOCXTECH GitHub repository](https://github.com/BLOCXTECH/BLOCX-Validator-Setup).

***

### Introduction

This guide provides detailed instructions for setting up and maintaining a BLOCX validator node. BLOCX uses a Proof of Stake (PoS) consensus mechanism, where validators are responsible for proposing and validating blocks on the blockchain.

By running a validator node, you contribute to the security and decentralization of the BLOCX network while earning rewards for your participation.

> **Note**: Running a validator node requires technical knowledge and a commitment to maintaining the node's uptime and security.

### Prerequisites

Before setting up your validator node, ensure you have:

* A Linux server (Ubuntu 20.04 LTS or later recommended)
* Root or sudo access to the server
* Stable internet connection with minimum 10 Mbps upload/download
* Dedicated IP address
* Basic knowledge of command line and Linux administration
* The required amount of BLOCX tokens for staking

### Hardware Requirements

For optimal performance of your validator node, we recommend:

| Component | Regular    | Recommended    |
| --------- | ---------- | -------------- |
| CPU       | 4 cores    | 8+ cores       |
| RAM       | 8 GB       | 16+ GB         |
| Storage   | 500 GB SSD | 1 TB+ NVMe SSD |
| Network   | 10 Mbps    | 25+ Mbps       |

> **Important**: Storage requirements will grow over time as the blockchain expands. Plan for future expansion.


---

# 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://blocx.gitbook.io/blocx./validator-node/introduction.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.