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

# Validator Node Explained

Validator nodes are lightweight nodes managed by the community. They play a crucial role in maintaining the protocol's integrity, enhancing its trustworthiness and security by validating TEE attestations on-chain.\ <br>

#### Validator Node Types and Tiers

&#x20;

<table data-header-hidden><thead><tr><th width="128"></th><th></th><th></th><th></th><th></th><th></th><th></th><th></th><th></th></tr></thead><tbody><tr><td>Node</td><td>Price (USDT)</td><td>Quantity</td><td>Purchase Phase</td><td>Airdrop per Node</td><td>Daily Output</td><td>1st Year Output</td><td>Cumulative 1st Year Output</td><td>Total Output per Node</td></tr><tr><td>Cloud Node</td><td>300</td><td>41800</td><td>Before TGE</td><td>8,288</td><td>160</td><td>58,400</td><td>66,688</td><td>300,288</td></tr><tr><td></td><td></td><td></td><td>After TGE</td><td>0</td><td>160</td><td>58,400</td><td>58,400</td><td>282,000</td></tr><tr><td>Rainy Node</td><td>600</td><td>9600</td><td>Before TGE</td><td>20,188</td><td>366</td><td>133,590</td><td>153,778</td><td>688,138</td></tr><tr><td></td><td></td><td></td><td>After TGE</td><td>0</td><td>366</td><td>133,590</td><td>133,590</td><td>667,950</td></tr><tr><td>Sunny Node</td><td>1500</td><td>1320</td><td>Before TGE</td><td>82,880</td><td>1,600</td><td>584,000</td><td>666,880</td><td>3,002,880</td></tr><tr><td></td><td></td><td></td><td>After TGE</td><td>0</td><td>1,600</td><td>584,000</td><td>584,000</td><td>2,920,000</td></tr></tbody></table>

#### Node Airdrop Mechanism

Only nodes purchased before the Token Generation Event (TGE) will receive an **one-time airdrop reward.**<br>

* After receiving the airdrop, $sNUBI will follow the conversion process outlined in the next section.

***

#### $sNUBI to $NUBI Conversion and Reward Withdrawal Mechanism

All mining rewards must be manually claimed by users. The following withdrawal rules apply:

* **30 Days:**
  * **Mining Output:** 100%
  * **Withdrawable Portion:** 25%
  * **Early Withdrawal Redistribution:**
    * Destroyed: 37.5%
    * Returned to Mining Reward Pool: 37.5%
* **60 Days:**
  * **Mining Output:** 100%
  * **Withdrawable Portion:** 50%
  * **Early Withdrawal Redistribution:**
    * Destroyed: 25%
    * Returned to Mining Reward Pool: 25%
* **180 Days:**
  * **Mining Output:** 100%
  * **Withdrawable Portion:** 100%
  * **Early Withdrawal Redistribution:**
    * Destroyed: 0%
    * Returned to Mining Reward Pool: 0%

***

#### Mining Reward Release

Node holders participate in network computing tasks by running nodes to earn mining rewards.

* **Nodes purchased before the TGE will receive a ONE TIME airdrop reward**
* Mining rewards account for **22.5% of the total token supply** and are released linearly each year.

This structure ensures fair distribution and prevents excessive early withdrawals.

***

Join Nubila's validator network today and contribute to building the largest ESG data oracle network. Secure your node and start participating in decentralized data validation!

{% embed url="<https://getwaitlist.com/waitlist/17088>" %}


---

# 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://nubila.gitbook.io/nubila/overview/nubila-validator-node-litepaper/validator-node-explained.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.