# Node Structure

#### Node Structure

**Full Node Functions**

* **Store Blockchain History:** Full nodes maintain the complete blockchain history on disk and can respond to data requests from the network.
* **Validate Blocks and Transactions:** Full nodes are responsible for receiving and validating new blocks and transactions.
* **Verify Account States:** Full nodes ensure the accuracy of account states.

**Supported Platforms**

* **Mac OS X**
* **Linux**
* **Windows**

**Suggested Requirements**

* **Operating System:** VPS with recent versions of Mac OS X, Linux, or Windows.
* **Disk Space:** 1 TB of free disk space on a solid-state drive (SSD) with gp3, 8k IOPS, 250 MB/S throughput, and read latency <1ms. (NVMe SSD is required if the node is started with snap sync)
* **CPU:** 16 cores
* **Memory (RAM):** 16 GB
* **Instance Type:** Recommended m5zn.3xlarge on AWS or c2-standard-16 on Google Cloud.
* **Internet Connection:** Broadband with upload/download speeds of 25 MB/S.

**Steps to Run a Full Node**

1. **Sync From Snapshot (Recommended):**
   * Download the pre-built binaries from the release page or follow the instructions provided.


---

# 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://optimusz7.gitbook.io/litepaper/for-developers/node-structure.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.