> 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/nubila-validator-node-interpretation/validator-node-types-and-mining.md).

# Validator Node Types & Mining

Validator nodes are the trust anchor of Nubila’s network. They validate sensor data, achieve consensus, and ensure only accurate, verified signals are anchored on-chain. To balance decentralization, security, and accessibility, Nubila offers three tiers of validator nodes — each with distinct roles, entry costs, and reward levels.

#### Node Tiers

☀️ Sunny Nodes

* Role: Finalize consensus, secure high-frequency data streams, and guarantee oracle-grade reliability.
* Requirements: Highest cost and responsibility.
* Rewards: Largest daily output and one-time pre-TGE airdrop, reflecting their critical role in settlement security.<br>

🌧 Rainy Nodes

* Role: Provide redundancy, cross-check results, and strengthen consensus across regions.
* Requirements: Moderate cost with balanced workload.
* Rewards: Medium daily output and pre-TGE airdrop, ideal for participants who want deeper involvement without heavy infrastructure.<br>

🌥 Cloud Nodes

* Role: Expand network coverage and run basic validations like CID checks and metadata verification.
* Requirements: Lowest cost; can be run by anyone via browser or lightweight client.
* Rewards: Smaller daily output, but crucial for decentralization and accessibility.\
  \
  Validator Node Types and Tiers

  &#x20;

  | Node       | Price (USDT) | Quantity | Purchase Phase | Airdrop per Node (sNUBI) | Daily Output (sNUBI) | 1st Year Output (sNUBI) | Cumulative 1st Year Output (sNUBI) | Total Output per Node (sNUBI) |
  | ---------- | ------------ | -------- | -------------- | ------------------------ | -------------------- | ----------------------- | ---------------------------------- | ----------------------------- |
  | Cloud Node | 300          | 41800    | Before TGE     | 8,288                    | 160                  | 58,400                  | 66,688                             | 300,288                       |
  |            |              |          | After TGE      | 0                        | 160                  | 58,400                  | 58,400                             | 282,000                       |
  | Rainy Node | 600          | 9600     | Before TGE     | 20,188                   | 366                  | 133,590                 | 153,778                            | 688,138                       |
  |            |              |          | After TGE      | 0                        | 366                  | 133,590                 | 133,590                            | 667,950                       |
  | Sunny Node | 1500         | 1320     | Before TGE     | 82,880                   | 1,600                | 584,000                 | 666,880                            | 3,002,880                     |
  |            |              |          | After TGE      | 0                        | 1,600                | 584,000                 | 584,000                            | 2,920,000                     |

***Note: Validator node mining will officially begin after the TGE — rewards only start once the network goes live.***

**Node Airdrop Mechanism**

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

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


---

# 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/nubila-validator-node-interpretation/validator-node-types-and-mining.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.