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

# Nubit

## Nubit Light Node Remote Service Hardware Requirements

* Single-core CPU
* 500 MB RAM
* 40 GB available storage space
* 10 Mbps bandwidth

## **Step 1: Purchase a Nubit node**

1. Login to app.satea.io and select Nubit
2. Select the number of nodes and node duration

After confirming that there are no errors, please follow the instructions to complete the payment.

## **Step 2:  Waiting for Node Configuration**

After the payment is completed, the system will automatically configure and synchronise the nodes. The system will automatically configure and synchronise the nodes after the payment is made. The process will be completed within 2 working days, and no additional operation is required during this period. You can click Nubit Node on the Node Management page to check the deployment progress and node details.

Once the configuration is complete, the platform will provide your Nubit PUBKEY on the Node Details page.

The above completes the deployment of the Nubit node.


---

# 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://satea.gitbook.io/satea/project-setup-guide/nubit.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.