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

# YAMATA Software

To complete the full **Validating Node (VN)** setup, users will need to install the **YAMATA software**, which provides all the necessary tools to operate the node, validate transactions, and take part in the order validation process. The software connects the node to the network, allowing it to perform validation tasks and interact with other nodes efficiently.

<figure><img src="/files/e8bK8N2HcQi0u6D5MNLo" alt=""><figcaption><p>YAMATA Software</p></figcaption></figure>

The minimum requirements for a single node license are as follows:

* **64MB RAM**
* **1 x86 CPU Core @ 2.1GHz**
* **10GB Disk Space**
* **10Mbps Internet Connection**

{above is placeholder information}


---

# 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.yamata.io/yamata-nodes/node-activation/yamata-software.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.