# Home

## **Welcome to Nitro Network- Where everybody wins!**

*Let’s start the journey of building decentralized private networks and empower people to build and monetize networks for next generation data, products and services.*

### Introduction

Nitro Network is building a world of private communication networks powered by IoT together with LoRaWAN/3G/4G and 5G. This hyperconnected world is the IoT alternative to cellular networks unlocking a $3 trillion market opportunity. We believe our decentralized private telecom networks is a gamechanger built on a blockchain with our proprietary token NCash at the core that drives utility and value from unlimited use cases. We are creating an inclusive ecosystem incentivizing users to own, operate and earn from the private networks of the future.

This document provides details on the Nitro vision, technology, token, rewards, as well as how to mine NCash, how to deploy and install Nitro Ion Miner, our path breaking concept of NFMs (Non- Fungible Miners) how to buy NFMs from the Nitro marketplace and becoming a Nester (hosting) on the Nitro platform. So let's begin!

In case you require further information, do join us on Discord and shoot out a text there. We will be happy to respond!

Thank you


# Introduction

To build and scale a private network, it is important to ensure a robust and uniform network coverage area. The two important factors for uniform network coverage are:

1. &#x20;Location of Ion miners and&#x20;
2. Radius of coverage area by every Ion miners

We figured that some of the common problems faced by other networks is that too many people are fighting for the same piece of the pie. So we decided to simplify this in a way where participants are entitled to their fair share of rewards.

How did we solve this problem? We defined the coverage area of a miner and were conscious not to include another miner within the same radius. Since two miners competing for network area within the same radius creates network congestion, we created exclusive radii in different locations. Miners are then placed within this defined radius.

Now the question arises - a) how will one participate if we have already defined the radius in different regions and there is already a miner? b) Can a person own more than one miner in this scenario?

Well we have a proper solution for this too. We are building a truly decentralized private network where literally anyone can be a participant. We are building an Airbnb-like platform where people living in our defined radius who show willingness to host a miner or someone else and get rewarded for hosting it. He/she will list their location and we will take care of the rest. While on the other side, a miner on the nitro network can purchase as many miners he/she wants and we will find a location for his/her miners to be installed. No matter where the miners are being hosted, miners will keep earning rewards and can track the earnings using the Nitro miner portal.

This way, we will always maintain the equilibrium of supply (location for hosts) and demand (Nitro ION miners) by ensuring uniform coverage area. The most crucial part is by doing so, each miner will enjoy maximum earning through mining rewards as there will be less competition among Nitro Ion miners for rewards.

This will allow us to occupy more coverage area with fewer miners. Not only this, by doing so we will be able to build a truly decentralized private network where people not only mine on the network but also facilitate the hosting of a miner for someone else by renting out their utilized space and monetizing the same.


# Nitro Mining Ecosystem

In order to build a scalable model and create a demand and supply equilibrium, we have introduced three concepts:

1. **Nesting**&#x20;

Nesting is a process by which we will ensure that we have strong connectivity in a defined radius of coverage area with a minimum number of Nitro ION miners.

&#x20; 2\. **Nitro NFM**

What is a Nitro NFM?&#x20;

We have come up with this unique concept of the Non-Fungible Miner (NFM). The NFM represents your miner and is your key to unlocking rewards when you mine on the Nitro Network. Since NFMs are much like NFTs, this means you will be able to mine on the Nitro Network without any mining hardware. Your NFM doubles up as your digital miner with which you can mine rewards instantly and effortlessly!

So how does this work? We have divided the NFMs (and hence the mystery boxes) into 3 tiers based on the location the NFM is being placed. Read more here

On the network, NFMs can mine NCash in every EPOCH - Nitro’s EPOCH is timed every thirty minutes. There are three rewards tiers

1. Tier 1 - ICONIC NFT&#x20;
2. Tier 2 - PREMIUM NFT&#x20;
3. Tier 3 - TOP NFT

The bot-themed NFMs have another function too. They are rare pieces of generative art (collectibles) - with accelerating value. So buying an NFM will place place the dual advantage of digital mining rewards and collectible art on your side!

On the ICONIC tier, you earn 95.69\* NCash, on the PREMIUM tier, you earn 52.05\* NCash and on the TOP tier, you earn 24.18\* NCash per EPOCH. It is important to remember that you need to be signed in to receive these rewards.

At the core of Nitro’s digital mining ecosystem is a trilogy - Nester and Miners bound together by Nitro platform. Here’s how it works

Nester host the nitro platform by getting their location (verified) by the Nitro platform. Hence, many such “nests” are created by participants hosting the network from their location across the world. Miners are those who build and support the network via NFMs (non-fungible miners) which they can buy from the marketplace. NFMs are representations of digital miners and are divided into Tiers based on their location. The Nitro platform creates the ideal Nester-Miner match to optimize reward distribution for both Nesters and Miners. Since Nitro Network has created a 1:1 grid (1 Nester in 1 km radius) we avoid any network congestion and at the same time ensure equitable distribution of rewards.

This is the synergy that powers Nitro’s digital mining with the Nitro platform as the protagonist in this ecosystem.


# Nester and Nesting

#### 1. **What is Nesting?**

Nesting is equivalent to hosting a network. Whoever participates in nesting and becomes a verified host on Nitro Network is called the nester. The Nitro platform enables this process of nesting, creating a synergy among people hosting the network across the world, enabling them to earn from their location.

Read more here

1. <https://nitronetwork.medium.com/nitro-nesting-an-effortless-way-to-earn-from-any-location-in-the-world-9df8777b8a1b2>
2. <https://nitronetwork.medium.com/why-nitro-nesting-ensures-everybody-wins-27f041d7c848>

**2. Why Nesting?**

"Nesting ensures that we have strong connectivity in a defined radius of coverage area with a minimum number of Nitro ION Miners. It addresses the two prime issues that can stand in the way of earning from a decentralized network. Network congestion - Normally the placement of miners are scattered and unoptimized. This creates network congestion in areas which are densely populated with miners, while there is weak coverage in other areas where there are less miners or no miners at all. Inequitable distribution of rewards- Due to uneven distribution of miners, multiple miners compete for a piece of the same pie when it comes to rewards.

By confining the radius and limiting the number of miners per radius, we are not only optimizing the resource utilization but also making sure every participant gets maximum rewards. Read more here: <https://nitronetwork.medium.com/why-nitro-nesting-ensures-everybody-wins-27f041d7c848>

#### 3. Who is a Nester?

Anybody who hosts the Nitro Network is a Nester. You can host your "nest" through the Nitro Platform anywhere in the world. You become a Nester when your location/address is verified and approved by the Nitro Network platform by fulfilling the required criteria.

#### 4. Why should you become a Nester?

Becoming a Nester on Nitro Network has many benefits. 1) You can earn effortlessly 2) Your location is your source of wealth. 3) It requires minimum investment. All you require is a small, unutilized space in your home/office, good WiFi connectivity and power supply.

#### 5. What are the steps for becoming a Nester?

You can become a Nester in 4 simple steps:

1. Choose your preferred unused micro space in your home/office
2. Register your location/address on the Nitro platform
3. Complete the verification process
4. Become a “nest"

#### 6. How will a Nester earn?

A nester will earn by participating actively in the Nitro Operating system (NOS), facilitating the hosting service and creating the private communication network infrastructure. Nesters will be required to keep the Nitro ION Miner active at all times in order to create wireless coverage and to respond to timely requests generated by NOS. They can also take part in staking and other incentive programs to maximize their earning.

#### 7. Do Nesters in specific locations have more benefits?

Nesting rewards are based on location. We have categorized cities into a Tier structure based on certain parameters such as population, infrastructure, footfall etc. More precisely, cities are categorized into Tier 1 (Iconic Tier) , Tier 2 ( Premium Tier) and Tier 3 (Top Location) in descending order. This means, if your current location falls in the Tier 1 category your rewards will be optimized as compared to Tier 2 or Tier 3 locations, simply by being in a prime location. There are rewards for Tier 2 or Tier 3 locations too! We have built the Tier structure in a way where everybody wins!

#### 8. Can there be multiple Nesters in the same place?

No. There can be only 1 Nester in a radius of 1 km

#### 9. How will I know my Tier?

All the locations from the cities across the globe will be categorized into different Tiers based on certain parameters as decided by Nitro Network. We will evaluate your location against these parameters and communicate the Tier in which your location falls when you get the nesting status.

#### 10. What if I no longer want to be a Nester?

You can delist your location or choose to become an inactive nest. We will pick a different address from our queue and allocate the Nitro ION Miner to a different address in the same defined radius.

#### 11. I live in a rented premises. In case I change my address, can I still be a Nester?

The nesting status of your location is address dependent. Since there can only be one Nester in a 1 km radius, we will evaluate the suitability of your new address against the Nitro parameters and communicate the same with you. If your new address falls in another radius, we will evaluate the availability of a nesting slot for your new address. If the same is available, we will assign you the nest slot, else you will be in the waitlisted category for nesting in the area.


# Introduction

### Introduction

NCash is the native cryptocurrency and protocol token of the Nitro Network. Its symbol is NCash. NCash is an AVAX native token that functions as a currency in the Nitro Network ecosystem.

<img src="https://lh5.googleusercontent.com/OLRxiSV3v8y2Mhkgu8LaO0ltAjg_78aD2Tzkzt2J-FK7ylUopqsnWuDEoFfGHNxYlIFNmRKgfqms1AzlZj3lIMtjuYIhRyo5b0ZCmuYrBc-ADSR4sXIKPZ1zoi4sWwNrYNkO2zb7" alt="" data-size="original">![](https://lh6.googleusercontent.com/IsL75olxicbyQ-GJYJmVHQgOms-d_W5ZV7BXDjjcLP2C2YAeTMVDlNCi9QgOe8Y87CBjLGocH-yfLUKiq1qcVEo4d4ZzlxTeLqMcOrtXIKMSLjsMqQaCZXOgAcD9BmhgwVTmPTtk)![](https://lh3.googleusercontent.com/jiyNRSs_9RjhYb028Eh8g9kiztd09LothzCX8vuYb0DyKz_VoDSx5cg58Xbb6W2gs2BWwAicmVibDeaUjh8sXsyYxsNG4DuS2Flf3RzoHCZwBuwM0mvIuwQhrMm3omHNC9gQupxm)![](https://lh3.googleusercontent.com/hk4yd2yJm1IGbjK1MJZYNb-LlzIPaE3d5TdA4visXHBTxCMwK4fcsqgi13FnHw2f_alPWs0NZxdcPfmbv38mAWascih9ahjEQ2nD-afDKXfI4xGNFjB6wphrooJN6-x_4Us7zAwY)

As Nitro Network's token, NCash creates the base for reward systems, incentive programs and liquidity programs. Currently, total supply of NCash is 10 billion. NCash is listed on following exchanges:​

### NCash- Token Usage

The NCash token is designed to serve the needs of the three parties primarily in the Nitro Network PCN (private communication network) ecosystem.

1. **Nester**: Mines NCash for hosting the Nitro ION Miner, maintaining the uptime and ensuring the network coverage in the respective area.
2. **Miner**: Mines NCash for facilitating the PCN infrastructure building and by participating in community incentive programs.&#x20;
3. **Enterprises and Developers**​: Use Nitro Network to connect devices and build IoT applications. NOS which is a USD-pegged utility token derived from NCash in a burn transaction, are used to pay transaction fees for wireless data transmissions on the network (in addition to things like adding Hotspots and sending).​


# Token Economics Principle

Nitro Network has adopted a similar token model as [Helium](https://docs.helium.com/blockchain/helium-token/) which consists of successfully implemented token economic concepts such as fixed max supply, inflationary model, and burn-and-mint equilibrium.

Nitro Network uses two distinct token economics concepts to ensure NCash supply is both plentiful for network needs but also relatively scarce, with a known maximum. Read our article on [token economics](https://nitronetwork.medium.com/nitro-networks-formerly-nucleus-vision-announces-token-model-same-as-helium-burn-and-mint-61fe1412634e).

#### **1. Max Supply: ​**

Nitro Network will have NCash as an inflationary token with a fixed max supply. It uses a two year halving schedule to reach the max supply (targeted to be achieved in 50 years\*)​

<mark style="color:red;">\*Number of years can be changed to maintain the demand and supply equation and to create optimum value for token</mark>

![](https://lh5.googleusercontent.com/5MIjXZgQMPPbhjS2QpZ7H4AlYbAcU32zsB7QIJWAg2bHHR7hTjDZXq8R2YHiAux9FBvf1gK6vFKbpo4Qu5xVd4xQuoLljwJLxj6_L4Rt2h_kSscZ2VmGFo6r3DSTm377idrZYeld)

#### 2. **NOS and Burn-and-Mint Economics**

Nitro uses two units of exchange- NCash and NOS, to execute Burn-and-Mint equilibrium​

1. **NCash**: NCash is native token of Nitro Network to be earned when Nitro ION Miners provide and validate wireless coverage, transfer device data over the network.
2. **NOS**: NOS are used by devices to send data on the network and for transaction fees. It is USD pegged with a fixed price. Network users buy NOS. Nitro Network burns NCash worth NOS purchase. It cannot be exchanged or converted back to USD.NOS allows users to transfer bytes of data and is USD pegged. The price of NOS is fixed and one NOS will always cost $0.00001. As mentioned above, NOS is purchased by paying in USD. After which Nitro Network burns NCash worth NOS purchase. Hence to buy 100,000 NOS, a user will pay $1. Thus, NCash worth $1 will be burnt. Let’s assume NCash current market price is $0.002. NCash = ($1/$0.002)= 500 NCash will be burnt. The market price of NCash will of course fluctuate, hence the amount NCash burnt will depend on its then current price.


# Token Distribution

![](https://lh5.googleusercontent.com/BUqBHDt7gfSMQVadF-Nbg6FKUl75OcH8XSdcGKrYrj6nqk7pIsCBwnc9pdYAnXBk6XVc1zBg2WA-2NtwjEeC3NuSD2Z0BIstwVENDeDF4aPNMpVF1CaiB3dOI4Ng-VJUhO6zNpT2)

### Token Distribution Schedule

<table data-header-hidden><thead><tr><th width="150" align="center"></th><th></th><th></th><th></th></tr></thead><tbody><tr><td align="center"><strong>Sno.</strong></td><td><strong>% to infrastructure</strong> </td><td><strong>% to Data Transfer</strong> </td><td><strong>% to Ecosystem Rewards</strong></td></tr><tr><td align="center">1</td><td>41.00%</td><td>24.00%</td><td>35.00%</td></tr><tr><td align="center">2</td><td>39.50%</td><td>26.50%</td><td>34.00%</td></tr><tr><td align="center">3</td><td>38.00%</td><td>29.00%</td><td>33.00%</td></tr><tr><td align="center">4</td><td>36.50%</td><td>31.50%</td><td>32.00%</td></tr><tr><td align="center">5</td><td>35.00%</td><td>34.00%</td><td>31.00%</td></tr><tr><td align="center">6</td><td>33.50%</td><td>36.50%</td><td>30.00%</td></tr><tr><td align="center">7</td><td>32.00%</td><td>39.00%</td><td>29.00%</td></tr><tr><td align="center">8</td><td>30.50%</td><td>41.50%</td><td>28.00%</td></tr><tr><td align="center">9</td><td>29.00%</td><td>44.00%</td><td>27.00%</td></tr><tr><td align="center">10</td><td>27.50%</td><td>46.50%</td><td>26.00%</td></tr><tr><td align="center">11</td><td>26.00%</td><td>49.00%</td><td>25.00%</td></tr><tr><td align="center">12</td><td>24.50%</td><td>51.50%</td><td>24.00%</td></tr><tr><td align="center">13</td><td>23.00%</td><td>54.00%</td><td>23.00%</td></tr><tr><td align="center">14</td><td>21.50%</td><td>56.50%</td><td>22.00%</td></tr><tr><td align="center">15</td><td>20.00%</td><td>59.00%</td><td>21.00%</td></tr><tr><td align="center">16</td><td>18.50%</td><td>61.50%</td><td>20.00%</td></tr><tr><td align="center">17</td><td>17.00%</td><td>64.00%</td><td>19.00%</td></tr><tr><td align="center">18</td><td>15.50%</td><td>66.50%</td><td>18.00%</td></tr><tr><td align="center">19</td><td>14.00%</td><td>69.00%</td><td>17.00%</td></tr><tr><td align="center">20</td><td>12.50%</td><td>71.50%</td><td>16.00%</td></tr><tr><td align="center">21</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">22</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">23</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">24</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">25</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">26</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">27</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">28</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">29</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">30</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">31</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">32</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">33</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">34</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">35</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">36</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">37</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">38</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">39</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">40</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">41</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">42</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">43</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">44</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">45</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">46</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">47</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">48</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">49</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr><tr><td align="center">50</td><td>11.00%</td><td>74.00%</td><td>15.00%</td></tr></tbody></table>


# Mining and Rewards

Earning a NCash token is multidimensional. Multiple complex equations are involved to calculate the earnings over a period of time. However, we will provide some simplified concepts for the community to cover their expected earnings.​ In this context, when it comes to reward we have kept in mind every possible stakeholder of our network.

&#x20;**How will you earn NCash token from Nitro Ion Miners?**

* The Nitro Network rewards miners and nesters for building network infrastructure and providing wireless coverage. They are rewarded in Nitro Network’s native Token which is NCash. ​
* Apart from the above, there are rewards for providing coverage, validation, data governance and security​.

How do Miners and Nesters earn NCash?

### Infrastructure Reward

| **Reward Type**                       | **Description**                                                                                                                                                                                             |
| ------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Network Infrastructure Mining Reward​ | Rewarded to the Miner and Nester for financing different assets such as Nitro ION Miners and underutilized space ​respectively.​                                                                            |
| Network Coverage Validation reward​   | Awarded to Nesters  whose Nitro Ion Miners respond to Sentinels - a compliance mechanism of the Nitro Operating System ( NOS ) that takes place every 30 minutes, for actively participating in the system. |
| Validator staking reward​             | Awarded to the people who participate in the Nitro validator staking programs. Distributed as per staked value and then current rate.                                                                       |

### Data Network Reward

| **Reward Type**                        | **Description**                                                                                                                                                                          |
| -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Network Data Transfer ​                | Distributed to Nitro ION Miners that route data for sensors on the Network actively. The amount of NCash is allocated proportionally based on the amount of data a Hotspot transferred.​ |
| Data, Security and Network Governance​ | Awarded to enterprise developers, miners and community for reporting, issue resolving and making the data network highly secure. ​                                                       |

### Team and Investors

| **Reward Type**       | **Description**                                                          |
| --------------------- | ------------------------------------------------------------------------ |
| Genesis Node rewards​ | Distributed to NCash holders who participate in Genesis Staking program​ |
| Ecosystem rewards​    | To be awarded to developers, core team members and key investors​        |

NCash will follow a mint-and-burn equilibrium model. The NCash minted will be utilized primarily for three things - Building Infrastructure, Data Network Rewards and Team & Investors. Each of these three major segments contain smaller units. For the first year infrastructure is 41%, Data Network is 24% and Team & Investors is 35%​. We will achieve this target using the parameter EPOCH\*

NCash will be minted every 30 minutes and will get distributed in different subsections of infrastructure, data network and team & investors. More information will be provided regarding this soon.

<mark style="color:red;">**\*Epoch = 30 minutes**</mark>

This will be distribution for the same:

|                                       |                |
| ------------------------------------- | -------------- |
| **Reward Type**                       | **Percentage** |
| I**nfrastructure Rewards**            | **41%**        |
| Network Infrastructure Mining Reward  | 53.00%         |
| Network Coverage Validation Reward    | 14.60%         |
| Validator Staking Reward​             | 32.40%         |
| **Data Network Rewards**              | **24%**        |
| Network Data Transfer                 | Upto 50%       |
| Data, Security and Network Governance | Upto 50%       |
| **Team and Investors**                | **35%**        |
| Genesis Node Rewards                  | 4%             |
| Ecosystem Rewards                     | 96%            |
| **Total**                             | 100%           |

**Note:**

* The Network Infrastructure Mining Reward gets distributed to Miners and Nesters in the ratio of 80:20.&#x20;
* The Network Coverage Validation Reward gets distributed based on how many times ION sensors respond to NOS (Nitro Operating System) sentinels.&#x20;
* Validator Staking Reward is for people who participate in the Nitro staking program and earn as per current APR and amount staked.&#x20;
* Network Data Transfer is dependent on data usage and data packets transfer data. The above mentioned percent is the upper limit for the same. In that case also, Miners and Nesters both get rewarded at the ratio of 80:20 of mining rewards by a particular ION miner.
* Minting of NCash tokens is subject to market conditions and factors which may have adverse impact for the community and company. Under certain conditions, minting and distribution of NCash will be controlled by Nitro Network, keeping every stakeholder’s benefits into consideration.

&#x20;


# LoRaWAN Introduction

LoRaWAN stands for Long Range Wide Area Network. It’s a standard for wireless communication that allows IoT (Internet of Things) devices to communicate over large distances with minimal battery usage.&#x20;

LoRaWAN is a point-to-multipoint networking protocol that uses Semtech’s LoRa modulation scheme. It’s not just about the radio waves; it’s about how the radio waves communicate with LoRaWAN Nitro ION Miners carry out functions like encryption and identification. It also includes a cloud component, which multiple Nitro ION Miners connect to.

A network based on the open LoRaWAN protocol is perfect for applications that require long-range or deep in-building communication among a large number of devices that have low power requirements and that collect small amounts of data.


# Advantages

* Long range (>5 km urban, >10 km suburban, >80 km VLOS)
* Long battery life (>10 years)
* Low cost (<$5/module)&#x20;
* 0.3 bps – 50 kbps, typically \~10 kB/day
* Secure
* Localization support
* Bidirectional


# Use Cases

![Use Cases](/files/thp2A1aPOcdNwjtcc7XV)

LoRaWAN allows for low power, long range but enables data rates. Use cases can typically be found in the IoT (Internet of Things), IoE (Internet of Everything) or M2M (Machine to Machine) areas. These areas mainly consist of sensors, devices and things that are battery-operated and communicate limited information on a limited interval.


# Nitro ION Miner

The Nitro ION miner encapsulates all that we have been creating. Based on a simple yet powerful concept, this indoor miner is very easy to set up and is the gateway for effortless earning from anywhere in the world! All that you need to set it up is a small unused space in your home/office or just any place, a good WiFi connection and power supply. And you are ON! Once the ION miner is connected to your Wifi and your account is linked and verified you begin earning. Incidentally, the ION miner supports major global frequencies, so rest assured it works just fine from anywhere!

### **Technical Specifications:**

* **LoRa Spec**:
  * 1 x SX1308 + 2 x 1257 LoRa Transceiver&#x20;
* **General Specification:**
  * 10M/100M RJ45 Ports x 1
  * 1 x 2.4G WiFi (802.11 bgn)
  * 1 x USB host port
  * Power Input via USB Type-C: 5V, 2A
* **Specifications**&#x20;
  * **Hardware System**:&#x20;
    * Linux Part:&#x20;
    * 400Mhz ar9331 processor&#x20;
    * 64MB RAM&#x20;
    * 16MB Flash
  * **Interface**
    * 10M/100M RJ45 Ports x 1&#x20;
    * WiFi : 802.11 b/g/n&#x20;
    * LoRaWAN Wireless&#x20;
    * Power Input: 5V DC, 2A, Type C&#x20;
    * USB 2.0 host connector x 1&#x20;
  * **Wifi Spec:**
    * IEEE 802.11 b/g/n&#x20;
    * Frequency Band: 2.4 \~ 2.462GHz&#x20;
  * **Tx power:**&#x20;
    * 11n tx power : mcs7/15: 11db mcs0 : 17db&#x20;
    * 11b tx power: 18db&#x20;
    * 11g 54M tx power: 12db&#x20;
    * 11g 6M tx power: 18db&#x20;
  * **Wifi Sensitivity:**
    * 11g 54M : -71dbm&#x20;
    * 11n 20M : -67dbm&#x20;
  * **LoRa Spec:**&#x20;
    * Up to -140 dBm sensitivity with SX1257 Tx/Rx front-end&#x20;
    * 70 dB CW interferer rejection at 1 MHz offset&#x20;
    * Able to operate with negative SNR, CCR up to 9dB&#x20;
    * Emulates 49 x LoRa demodulators and 1 x (G)FSK demodulator&#x20;
    * Dual digital TX & RX radio front-end interfaces&#x20;
    * 10 programmable parallel demodulation paths&#x20;
    * Dynamic data-rate (DDR) adaptation&#x20;
    * True antenna diversity or simultaneous dual-band operation&#x20;
  * **Max Power: 5v, 1.3A**


# Organizationally Unique Identifier

Each Network Server on the Nitro Network acquires an Organizationally Unique Identifier (OUI).

### **Join-request and join-accept messages**

To participate in the Nitro Network, each end-device has to be personalized and activated.

A LoRaWAN device can be defined by (AppEui, DevEui) and DevAddrs has to be allocated during the join procedure.

The join-request/accept messages are used by the over-the-air activation procedure for roaming purposes.

#### **Join-request message**

The join procedure is always initiated from the end-device by sending a join-request message.

![](/files/tbWTv6l4QTPCIAqLNwcA)

#### **Join-accept message**

The network server will respond to the join-request message with a join-accept message if the end-device is permitted to join a network.

![](/files/gPmagF99QGZYa9WnTgUS)

#### **Data Stored in the End-Device after Activation**

After activation, the following information is stored in the end-device: a device address (DevAddr), an application identifier (AppEUI), a network session key (NwkSKey), and an application session key (AppSKey).

The DevAddr identifies the end-device within the current network.&#x20;

DevAddr consists of a network identifier and network address.

![](/files/XR2ZHkkuHjXxK1vMOpir)

The network identifier (NwkID) used to separate addresses of territorially overlapping networks of different network operators and to remedy roaming issues.

The network address (NwkAddr) of the end-device, can be arbitrarily assigned by the network manager.


# Roaming on Nitro Network

## Roaming Architecture&#x20;

### **Network Reference Model**

Figure 1 and Figure 2 shows the Network Reference Model (NRM) for the LoRaWAN architecture.

![Figure 1: LoRaWan Network Reference Model (NRM), End-Device at Home](/files/929QN2xyYUcxEzA1Bank)

### Roaming Architecture Model

![](/files/vNyq2WGWtLEHvONUw9kq)

### **End-Device**

The end-device is a sensor or an actuator. The end-device is wirelessly connected to a LoRaWAN network through Nitro ION Miners. The application layer of the end-device is connected to a specific Application Server in the cloud. All application layer payloads of this end-device are routed to its corresponding Application Server.


# Network Server

### **Nitro ION Miner**

The Nitro ION Miner forwards all received LoRaWAN radio packets to the Network Server that is connected through an IP back-bone. The Nitro ION Miner operates entirely at the physical layer. Its role is simply to decode uplink radio packets from the air and forward them unprocessed to the Network Server. Conversely, for downlinks, the Nitro ION Miner simply executes transmission requests coming from the Network Server without any interpretation of the payload.

### **LoRaWAN Network Server**

The Network Server (NS) terminates the LoRaWAN MAC layer for the end-devices connected to the network. It is the center of the star topology. Each NS is identified by a unique NSID (an IEEE EUI64 identifier), and can be configured with one or more NetIDs.

Generic features of NS are:

• End-Device address check

• Frame authentication and frame counter checks

• Acknowledgements

• Data rate adaptation

• Responding to all MAC layer requests coming from the end-device

• Forwarding uplink application payloads to the appropriate Application Servers

• Queuing of downlink payloads coming from any Application Server to any End-connected to the network

• Forwarding Join-request and Join-accept messages between the end-devices and  the Join Servers

In a roaming architecture, an NS may play three different roles depending on whether the end-device is in roaming situation or not, and the type of roaming that Serving NS (sNS) controls the MAC layer of the end-device.

Home NS (hNS) is where Device Profile, Service Profile, Routing Profile and DevEUI of the end-device are stored. hNS has a direct relation with the Join Server that will be used for the Join Procedure. It is connected to the Application Server (AS). When hNS and sNS are separated, they are in a roaming agreement. Uplink and downlink packets are forwarded between the sNS and the hNS.

Forwarding NS (fNS) is the NS managing the Radio Nitro ION Miners. When sNS and fNS are separated, they are in a roaming agreement. There may be one or more fNS serving the end-device. Uplink and downlink packets are forwarded between the fNS and the sNS.

### **Join the Network Server**

The Join Server (JS) manages the Over-the-Air (OTA) end-device activation process. There may be several JSs connected to a NS, and a JS may connect to several NSs.

The end-device signals which JS should be interrogated through the JoinEUI field of the Join-request message. Each JS is identified by a unique JoinEUI value. Note that the App EUI field of the Join-request in LoRaWAN 1.0/1.0.2 \[LW10, LW102] is renamed to JoinEUI field in LoRaWAN 1.1\[LW11]. The term JoinEUI is used to refer to the AppEUI in the context of LoRaWAN 1.0/1.0.2 end-devices in this specification.

The JS knows the end-device’s Home Network Server identifier and provides that information to the other Network Servers when required by the roaming procedures.

The JS contains the required information to process uplink Join-request frames and generate the downlink Join-accept frames. It also performs the network and application session key derivations. It communicates the Network Session Key of the end-device to the NS, and the Application Session Key to the corresponding Application Server.

For that purpose the JS shall contain the following information for each end-device under its control :

• DevEUI

• AppKey

• NwkKey (only applicable to LoRaWAN 1.1 end-device)

• Home Network Server identifier

• Application Server identifier

• A way to select the preferred network in case several networks can serve the  end-device

• LoRaWAN version of the end-device (LoRaWAN 1.0, 1.0.2, or 1.1)

The root keys NwkKey and AppKey are only available in the JS and the end-device, and they are never sent to the NS nor the AS.

Secure provisioning, storage, and usage of root keys NwkKey and AppKey on the end-device and the backend are intrinsic to the overall security of the solution. These are left to implementation and out of scope of this document. However, elements of this solution may include SE (Secure Elements) and HSM (Hardware Security Modules).

The way that information is actually programmed into the JS is outside the scope of this document and may vary from one JS to another. This may be through a web portal for example or via a set of APIs.

The JS and the NS shall be able to establish secure communication which provides end-point authentication, integrity & replay protection, and confidentiality. The JS shall also be able to securely deliver Application Session Key to the Application Server.

The JS may be connected to several Application Servers (AS), and an AS may be connected to several JSs.

The JS and the AS shall be able to establish secure communication which provides end-point authentication, integrity, replay protection, and confidentiality.

### **Application Server**&#x20;

The Application Server (AS) handles all the application layer payloads of the associated end-devices and provides the application-level service to the end-user. It also generates all the application layer downlink payloads towards the connected end-devices.

There may be multiple ASs connected to a NS, and an AS may be connected to several NSs (operating end-devices through several networks, for example). An AS may also be connected to multiple JSs.

The Home NS routes the uplinks toward the appropriate AS based on the DevEUI.

In addition to the aforementioned network elements, LoRaWAN architecture defines the following network interfaces among these entities:

1. hNS-JS: This interface is used for supporting the Join (Activation) Procedure between the JS and the NS.
2. vNS-JS: This interface is used for Roaming Activation Procedure. It is used to retrieve the NSID and NetID of the hNS associated with the end-device.
3. ED-NS: This interface is used for supporting LoRaWAN MAC-layer signaling and payload delivery between the end-device and the NS.
4. AS-hNS: This interface is used for supporting delivery of application payload and also the associated meta-data between the AS and the NS.
5. hNS-sNS: This interface is used for supporting roaming signaling and payload delivery between the hNS and the sNS.
6. sNS-fNS: This interface is used for supporting roaming signaling and payload delivery between the sNS and the fNS.
7. AS-JS: This interface is used for delivering Application Session Key from the JS to the AS.

<br>


# Frequency Bands

Nitro’s LoRaWAN Network supports the following frequencies:&#x20;

* US 915
* EU 868&#x20;
* CN 470 - In progress
* AU 915 - In progress


# Uplink, Downlink

| **US 915**                                                                                               | <p><br></p>                        |
| -------------------------------------------------------------------------------------------------------- | ---------------------------------- |
| **Uplink**                                                                                               | <p><br></p>                        |
| **Frequency (MHZ)**                                                                                      | **Spreading Factor**               |
| 903.9                                                                                                    | SF7BW125 to SF10BW125              |
| 904.1                                                                                                    | SF7BW125 to SF10BW125              |
| 904.3                                                                                                    | SF7BW125 to SF10BW125              |
| 904.5                                                                                                    | SF7BW125 to SF10BW125              |
| 904.7                                                                                                    | SF7BW125 to SF10BW125              |
| 904.9                                                                                                    | SF7BW125 to SF10BW125              |
| 905.1                                                                                                    | SF7BW125 to SF10BW125              |
| 905.3                                                                                                    | SF7BW125 to SF10BW125              |
| 904.6                                                                                                    | SF8BW500                           |
| **Downlink**                                                                                             | <p><br></p>                        |
| **Frequency (MHZ)**                                                                                      | **Spreading Factor**               |
| 923.3                                                                                                    | SF7BW500 to SF12BW500 (RX1)        |
| 923.9                                                                                                    | SF7BW500 to SF12BW500 (RX1)        |
| 924.5                                                                                                    | SF7BW500 to SF12BW500 (RX1)        |
| 925.1                                                                                                    | SF7BW500 to SF12BW500 (RX1)        |
| 925.7                                                                                                    | SF7BW500 to SF12BW500 (RX1)        |
| 926.3                                                                                                    | SF7BW500 to SF12BW500 (RX1)        |
| 926.9                                                                                                    | SF7BW500 to SF12BW500 (RX1)        |
| 927.5                                                                                                    | SF7BW500 to SF12BW500 (RX1)        |
| 923.3                                                                                                    | SF12BW500 (RX2)                    |
| **EU868**                                                                                                | <p><br></p>                        |
| **Uplink**                                                                                               | <p><br></p>                        |
| **Frequency (MHZ)**                                                                                      | **Spreading Factor**               |
| 868.1                                                                                                    | SF7BW125 to SF12BW125              |
| 868.3                                                                                                    | SF7BW125 to SF12BW125 and SF7BW250 |
| 868.5                                                                                                    | SF7BW125 to SF12BW125              |
| 867.1                                                                                                    | SF7BW125 to SF12BW125              |
| 867.3                                                                                                    | SF7BW125 to SF12BW125              |
| 867.5                                                                                                    | SF7BW125 to SF12BW125              |
| 867.7                                                                                                    | SF7BW125 to SF12BW125              |
| 867.9                                                                                                    | SF7BW125 to SF12BW125              |
| 868.8                                                                                                    | FSK                                |
| **Downlink**                                                                                             | <p><br></p>                        |
| <ul><li>Uplink channels 1-9 (RX1)</li><li><strong>869.525</strong> - SF9BW125 (RX2)</li></ul><p><br></p> | <p><br><br><br></p>                |
| **CN470**                                                                                                | <p><br></p>                        |
| **Uplink**                                                                                               | <p><br></p>                        |
| **Frequency (MHZ)**                                                                                      | **Spreading Factor**               |
| 486.3                                                                                                    | SF7BW125 to SF12BW125              |
| 486.5                                                                                                    | SF7BW125 to SF12BW125              |
| 486.7                                                                                                    | SF7BW125 to SF12BW125              |
| 486.9                                                                                                    | SF7BW125 to SF12BW125              |
| 487.1                                                                                                    | SF7BW125 to SF12BW125              |
| 487.3                                                                                                    | SF7BW125 to SF12BW125              |
| 487.5                                                                                                    | SF7BW125 to SF12BW125              |
| 487.7                                                                                                    | SF7BW125 to SF12BW125              |
| **Downlink**                                                                                             | <p><br></p>                        |
| **Frequency (MHZ)**                                                                                      | **Spreading Factor**               |
| 506.7                                                                                                    | SF7BW125 to SF12BW125 (RX1)        |
| 506.9                                                                                                    | SF7BW125 to SF12BW125 (RX1)        |
| 507.1                                                                                                    | SF7BW125 to SF12BW125 (RX1)        |
| 507.3                                                                                                    | SF7BW125 to SF12BW125 (RX1)        |
| 507.5                                                                                                    | SF7BW125 to SF12BW125 (RX1)        |
| 507.7                                                                                                    | SF7BW125 to SF12BW125 (RX1)        |
| 507.9                                                                                                    | SF7BW125 to SF12BW125 (RX1)        |
| 508.1                                                                                                    | SF7BW125 to SF12BW125 (RX1)        |
| 505.3                                                                                                    | SF12BW125 (RX2)                    |
| **AU915**                                                                                                | <p><br></p>                        |
| **Uplink**                                                                                               | <p><br></p>                        |
| **Frequency (MHZ)**                                                                                      | **Spreading Factor**               |
| 916.8                                                                                                    | SF7BW125 to SF12BW125              |
| 917                                                                                                      | SF7BW125 to SF12BW125              |
| 917.2                                                                                                    | SF7BW125 to SF12BW125              |
| 917.4                                                                                                    | SF7BW125 to SF12BW125              |
| 917.6                                                                                                    | SF7BW125 to SF12BW125              |
| 917.8                                                                                                    | SF7BW125 to SF12BW125              |
| 918                                                                                                      | SF7BW125 to SF12BW125              |
| 918.2                                                                                                    | SF7BW125 to SF12BW125              |
| 917.5                                                                                                    | SF8BW500                           |
| **Downlink**                                                                                             | <p><br></p>                        |
| **Frequency (MHZ)**                                                                                      | **Spreading Factor**               |
| 923.3                                                                                                    | SF7BW500 to SF12BW500 (RX1)        |
| 923.9                                                                                                    | SF7BW500 to SF12BW500 (RX1)        |
| 924.5                                                                                                    | SF7BW500 to SF12BW500 (RX1)        |
| 925.1                                                                                                    | SF7BW500 to SF12BW500 (RX1)        |
| 925.7                                                                                                    | SF7BW500 to SF12BW500 (RX1)        |
| 926.3                                                                                                    | SF7BW500 to SF12BW500 (RX1)        |
| 926.9                                                                                                    | SF7BW500 to SF12BW500 (RX1)        |
| 927.5                                                                                                    | SF7BW500 to SF12BW500 (RX1)        |
| 923.3                                                                                                    | SF12BW500 (RX2)                    |


# Country Wise Bands

| **Country**                                  | **Frequency Plan**               |
| -------------------------------------------- | -------------------------------- |
| Afghanistan                                  | <p><br></p>                      |
| Albania                                      | EU868                            |
| Algeria                                      | AS923\_3                         |
| American Samoa                               | US915                            |
| Andorra                                      | EU868                            |
| Angola                                       | EU433                            |
| Anguilla                                     | AU915                            |
| Antarctica                                   | <p><br></p>                      |
| Antigua and Barbuda                          | <p><br></p>                      |
| Argentina                                    | AU915-928                        |
| Armenia                                      | EU868                            |
| Aruba                                        | <p><br></p>                      |
| Australia                                    | AU915-928                        |
| Austria                                      | <p>EU863-870</p><p>EU433</p>     |
| Azerbaijan                                   | EU433                            |
| Bahamas                                      | US915                            |
| Bahrain                                      | <p>EU863-870</p><p>EU433</p>     |
| Bangladesh                                   | AS923\_1                         |
| Barbados                                     | AU915                            |
| Belarus                                      | EU868                            |
| Belgium                                      | <p>EU863-870</p><p>EU433</p>     |
| Belize                                       | AU915                            |
| Benin                                        | EU868                            |
| Bermuda                                      | US915                            |
| Bhutan                                       | EU868                            |
| Bolivia                                      | US902-928                        |
| Bosnia and Herzegovina                       | <p>EU863-870</p><p>EU433</p>     |
| Botswana                                     | <p>EU863-870</p><p>EU433</p>     |
| Bouvet Island                                | EU868                            |
| Brazil                                       | AU915-928                        |
| British Indian Ocean Territory               | <p><br></p>                      |
| British Virgin Islands                       | AU915                            |
| Brunei                                       | AS923-925 (“AS2”)                |
| Bulgaria                                     | <p>EU863-870</p><p>EU433</p>     |
| Burkina Faso                                 | <p><br></p>                      |
| Burundi                                      | EU868                            |
| Cambodia                                     | AS923-925 (“AS2”)                |
| Cameroon                                     | EU433                            |
| Canada                                       | US902-928                        |
| Cape Verde                                   | <p><br></p>                      |
| Cayman Islands                               | US915                            |
| Central African Republic                     | <p><br></p>                      |
| Chad                                         | <p><br></p>                      |
| Chile                                        | AU915-928                        |
| China                                        | <p>CN470-510</p><p>CN779-787</p> |
| Christmas Island                             | AU915                            |
| Cocos \[Keeling] Islands                     | AU915                            |
| Colombia                                     | US902-928                        |
| Comoros                                      | EU868                            |
| Congo \[DRC]                                 | <p>EU863-870</p><p>EU433</p>     |
| Congo \[Republic]                            | <p><br></p>                      |
| Cook Islands                                 | AU915                            |
| Costa Rica                                   | US902-928                        |
| Côte d'Ivoire                                | EU868                            |
| Croatia                                      | <p>EU863-870</p><p>EU433</p>     |
| Cuba                                         | AS923\_3                         |
| Cyprus                                       | <p>EU863-870</p><p>EU433</p>     |
| Czech Republic                               | <p>EU863-870</p><p>EU433</p>     |
| Denmark                                      | <p>EU863-870</p><p>EU433</p>     |
| Djibouti                                     | <p><br></p>                      |
| Dominica                                     | AU915                            |
| Dominican Republic                           | US902-928                        |
| Ecuador                                      | US902-928                        |
| Egypt                                        | EU868                            |
| El Salvador                                  | AU915                            |
| Equatorial Guinea                            | EU868                            |
| Eritrea                                      | <p><br></p>                      |
| Estonia                                      | <p>EU863-870</p><p>EU433</p>     |
| Eswatini \[Swaziland]                        | <p>EU863-870</p><p>EU433</p>     |
| Ethiopia                                     | <p><br></p>                      |
| Falkland Islands \[Islas Malvinas]           | EU868                            |
| Faroe Islands                                | EU868                            |
| Fiji                                         | <p><br></p>                      |
| Finland                                      | <p>EU863-870</p><p>EU433</p>     |
| France                                       | <p>EU863-870</p><p>EU433</p>     |
| French Guiana                                | EU868                            |
| French Polynesia                             | EU868                            |
| French Southern Territories                  | EU868                            |
| Gabon                                        | <p><br></p>                      |
| Gambia                                       | EU433                            |
| Gaza Strip                                   | <p><br></p>                      |
| Georgia                                      | EU868                            |
| Germany                                      | <p>EU863-870</p><p>EU433</p>     |
| Ghana                                        | EU433                            |
| Gibraltar                                    | EU868                            |
| Greece                                       | <p>EU863-870</p><p>EU433</p>     |
| Greenland                                    | EU868                            |
| Grenada                                      | AU915                            |
| Guadeloupe                                   | EU868                            |
| Guam                                         | US915                            |
| Guatemala                                    | AU915                            |
| Guernsey                                     | EU868                            |
| Guinea                                       | EU433                            |
| Guinea-Bissau                                | <p><br></p>                      |
| Guyana                                       | US902-928                        |
| Haiti                                        | <p><br></p>                      |
| Heard Island and McDonald Islands            | AU915                            |
| Honduras                                     | AU915                            |
| Hong Kong                                    | AS923-925 (“AS2”)                |
| Hungary                                      | <p>EU863-870</p><p>EU433</p>     |
| Iceland                                      | <p>EU863-870</p><p>EU433</p>     |
| India                                        | IN865-867                        |
| Indonesia                                    | AS923-925 (“AS2”)                |
| Iran                                         | EU868                            |
| Iraq                                         | <p><br></p>                      |
| Ireland                                      | <p>EU863-870</p><p>EU433</p>     |
| Isle of Man                                  | EU868                            |
| Israel                                       | AS923\_4                         |
| Italy                                        | <p>EU863-870</p><p>EU433</p>     |
| Jamaica                                      | AU915                            |
| Japan                                        | AS920-923 (“AS1”)                |
| Jersey                                       | EU868                            |
| Jordan                                       | IN865                            |
| Kazakhstan                                   | EU433                            |
| Kenya                                        | EU868                            |
| Kiribati                                     | <p><br></p>                      |
| Kosovo                                       | <p><br></p>                      |
| Kuwait                                       | EU868                            |
| Kyrgyzstan                                   | <p><br></p>                      |
| Laos                                         | AS923-925 (“AS2”)                |
| Latvia                                       | <p>EU863-870</p><p>EU433</p>     |
| Lebanon                                      | EU868                            |
| Lesotho                                      | <p>EU863-870</p><p>EU433</p>     |
| Liberia                                      | <p><br></p>                      |
| Libya                                        | <p><br></p>                      |
| Liechtenstein                                | <p>EU863-870</p><p>EU433</p>     |
| Lithuania                                    | <p>EU863-870</p><p>EU433</p>     |
| Luxembourg                                   | <p>EU863-870</p><p>EU433</p>     |
| Macau                                        | AS923\_1                         |
| North Macedonia                              | <p>EU863-870</p><p>EU433</p>     |
| Madagascar                                   | <p>EU863-870</p><p>EU433</p>     |
| Malawi                                       | <p>EU863-870</p><p>EU433</p>     |
| Malaysia                                     | AS920-923 (“AS1”)                |
| Maldives                                     | <p><br></p>                      |
| Mali                                         | EU433                            |
| Malta                                        | <p>EU863-870</p><p>EU433</p>     |
| Marshall Islands                             | <p><br></p>                      |
| Martinique                                   | EU868                            |
| Mauritania                                   | EU868                            |
| Mauritius                                    | <p>EU863-870</p><p>EU433</p>     |
| Mayotte                                      | EU868                            |
| Mexico                                       | US902-928                        |
| Micronesia                                   | <p><br></p>                      |
| Moldova                                      | <p>EU863-870</p><p>EU433</p>     |
| Monaco                                       | EU868                            |
| Mongolia                                     | <p><br></p>                      |
| Montenegro                                   | <p>EU863-870</p><p>EU433</p>     |
| Montserrat                                   | AU915                            |
| Morocco                                      | EU433                            |
| Mozambique                                   | <p>EU863-870</p><p>EU433</p>     |
| Myanmar \[Burma]                             | AS923\_1                         |
| Namibia                                      | <p>EU863-870</p><p>EU433</p>     |
| Nauru                                        | <p><br></p>                      |
| Nepal                                        | <p><br></p>                      |
| Netherlands                                  | <p>EU863-870</p><p>EU433</p>     |
| Netherlands Antilles                         | <p><br></p>                      |
| New Caledonia                                | EU868                            |
| New Zealand                                  | AU915-928                        |
| Nicaragua                                    | AU915                            |
| Niger                                        | IN865                            |
| Nigeria                                      | EU868                            |
| Niue                                         | AU915                            |
| Norfolk Island                               | AU915                            |
| North Korea                                  | <p><br></p>                      |
| Northern Mariana Islands                     | US915                            |
| Norway                                       | EU868                            |
| Oman                                         | EU868                            |
| Pakistan                                     | IN865                            |
| Palau                                        | <p><br></p>                      |
| Palestinian Territories                      | <p><br></p>                      |
| Panama                                       | US902-928                        |
| Papua New Guinea                             | AU915                            |
| Paraguay                                     | US902-928                        |
| Peru                                         | US902-928                        |
| Philippines                                  | <p>EU863-870</p><p>EU433</p>     |
| Pitcairn Islands                             | <p><br></p>                      |
| Poland                                       | <p>EU863-870</p><p>EU433</p>     |
| Portugal                                     | <p>EU863-870</p><p>EU433</p>     |
| Puerto Rico                                  | US902-928                        |
| Qatar                                        | EU868                            |
| Réunion                                      | EU868                            |
| Romania                                      | <p>EU863-870</p><p>EU433</p>     |
| Russia                                       | <p>EU863-870</p><p>EU433</p>     |
| Rwanda                                       | EU868                            |
| Saint Helena                                 | <p><br></p>                      |
| Saint Kitts and Nevis                        | AU915                            |
| Saint Lucia                                  | AU915                            |
| Saint Pierre and Miquelon                    | EU868                            |
| Saint Vincent and the Grenadines             | AU915                            |
| Samoa                                        | EU868                            |
| San Marino                                   | EU868                            |
| São Tomé and Príncipe                        | <p><br></p>                      |
| Saudi Arabia                                 | <p>EU863-870</p><p>EU433</p>     |
| Senegal                                      | EU868                            |
| Serbia                                       | <p>EU863-870</p><p>EU433</p>     |
| Seychelles                                   | <p>EU863-870</p><p>EU433</p>     |
| Sierra Leone                                 | <p><br></p>                      |
| Singapore                                    | AS920-923 (“AS1”)                |
| Slovakia                                     | <p>EU863-870</p><p>EU433</p>     |
| Slovenia                                     | <p>EU863-870</p><p>EU433</p>     |
| Solomon Islands                              | AS923\_1                         |
| Somalia                                      | EU868                            |
| South Africa                                 | <p>EU863-870</p><p>EU433</p>     |
| South Georgia and the South Sandwich Islands | EU868                            |
| South Korea                                  | KR920-923                        |
| Spain                                        | <p>EU863-870</p><p>EU433</p>     |
| Sri Lanka                                    | AS923\_1                         |
| Sudan                                        | <p><br></p>                      |
| Suriname                                     | US902-928                        |
| Svalbard and Jan Mayen                       | EU868                            |
| Sweden                                       | <p>EU863-870</p><p>EU433</p>     |
| Switzerland                                  | <p>EU863-870</p><p>EU433</p>     |
| Syria                                        | EU868                            |
| Taiwan                                       | AS923-925 (“AS2”)                |
| Tajikistan                                   | <p><br></p>                      |
| Tanzania                                     | <p>EU863-870</p><p>EU433</p>     |
| Thailand                                     | AS923-925 (“AS2”)                |
| Timor-Leste                                  | <p><br></p>                      |
| Togo                                         | EU433                            |
| Tokelau                                      | AU915                            |
| Tonga                                        | AU915                            |
| Trinidad and Tobago                          | AU915                            |
| Tunisia                                      | EU868                            |
| Turkey                                       | <p>EU863-870</p><p>EU433</p>     |
| Turkmenistan                                 | <p><br></p>                      |
| Turks and Caicos Islands                     | AU915                            |
| Tuvalu                                       | <p><br></p>                      |
| U.S. Minor Outlying Islands                  | US915                            |
| U.S. Virgin Islands                          | US915                            |
| Uganda                                       | IN865                            |
| Ukraine                                      | EU868                            |
| United Arab Emirates                         | <p>EU863-870</p><p>EU433</p>     |
| United Kingdom                               | <p>EU863-870</p><p>EU433</p>     |
| United States                                | US902-928                        |
| Uruguay                                      | US902-928                        |
| Uzbekistan                                   | EU433                            |
| Vanuatu                                      | AS923\_3                         |
| Vatican City                                 | <p>EU863-870</p><p>EU433</p>     |
| Venezuela                                    | US902-928                        |
| Vietnam                                      | AS923-925 (“AS2”)                |
| Wallis and Futuna                            | EU868                            |
| Western Sahara                               | <p><br></p>                      |
| Yemen                                        | <p><br></p>                      |
| Zambia                                       | <p>EU863-870</p><p>EU433</p>     |
| Zimbabwe                                     | <p>EU863-870</p><p>EU433</p>     |


# Access and conﬁgure NNIONGIN

The NNIONGIN is conﬁgured as a WiFi Access Point by factory default. You can access and conﬁgure the NNIONGIN after connecting to its WiFi network or via its WAN Ethernet port.

## 1. Find the IP address of NNIONGIN

### 1.1 Connect via WiFi

<figure><img src="https://lh6.googleusercontent.com/DJ_B4NpTtXwunM4cEKpGhe8R9L8_cjopSwaJpOY_ri1AC8afgxtNMMvM-yzA66KIpHcxOACa9M4TD1hk2Len_Sn82VJC7z8i7-GKs1jNBR-E05Q0vyhsjYfD02NFTy84mZXuOZ-RiHUInxUs7Rw8JhliZwLVcSKhV2uajRqu4uJiXZ3XFAkhqx9642sO0A" alt=""><figcaption></figcaption></figure>

At the ﬁrst boot of NNIONGIN, it will auto-generate a WiFi network called NitroGW-Idr-xxxxxx with the password: \*\*\*\*\*\*

<figure><img src="https://lh6.googleusercontent.com/Hfkniv32E6HpqVg-49hO4EN8N8kZWFFqdMwj9u3Qv4xyO2VmRlyb_qb1Lb-MY7VvpWJF6pQJ0ncO6SwBLxPOTQRDOqBc0sqTZVMx3G-hCbY3KtanIVSEVTNHeU_0AUpd-MUe77lUwyRNSatU5-isSInlnFFXSAh-sQXP93ffOVHkNoLsyw8UixuqZz-lTw" alt=""><figcaption></figcaption></figure>

Users can use a PC to connect to this WiFi network. The PC will get an IP address 10.130.76.xxx, and the NNIONGIN has the default IP 10.130.76.1

### 1.2 Connect via Ethernet with DHCP IP from the router

<figure><img src="https://lh3.googleusercontent.com/u6xeniMCV2juxQQTtCs078yQwGdq8cleWaBKUZuwrcr7v4sUhs4qcaiZoLXiOOV67Q1Y8mMEyPaBIewBLRA6YrD-s4GxAioyKrYBOCFeKhD4rqwWuS3ufyHanxWWQ2MmsjExt3C5Qj4Ild_kvLupmT4Ipg2I3Y9cTrmfz8mYbce8OXrD8OVMW0nTQEzAFw" alt=""><figcaption></figcaption></figure>

Alternatively, connect the NNIONGIN Ethernet port to your router, and NNIONGIN will obtain an IP address from your router. In the router's management portal, you should be able to ﬁnd what IP address the router has assigned to the NNIONGIN. You can also use this IP to connect.

### 1.3 Connect via WiFi with DHCP IP from the router

<figure><img src="https://lh4.googleusercontent.com/QYrd71iBUQaAraGyGN_DhJKea6i5OsTOJ6XNLEkmt9FERaz4DDqVVSxpssCwOXyCbhd0aqJWCoxEs083GYw0HLsUtvniUdKVhZ05F9O3yOcCFV4eBxs_uFEgvxyDgLTVmG0MlGfJsRxsxUmR3M9TGC8ymxW3kSloRsSVpLLJAP8M2U692eRMTy8wHpGPGA" alt=""><figcaption></figcaption></figure>

If the NNIONGIN already connects to the router via WiFi, users can use the WiFi IP to connect to NNIONGIN.

## 2. Access conﬁgure web UI

### Web Interface

1. Open a browser on the PC and type the NNIONGIN ip address (depends on your connect method) [http://10.130.76.1/](http://10.130.1.1/) (Access via WiFi AP network) or
2. <http://IP\\_ADDRESS> or http\:// IP\_ADDRESS:8000. You will see the login interface of NNIONGIN as shown below.

The account details for Web Login are:

**Username: admin**

**Password: \*\*\*\*\*\***

<figure><img src="https://lh6.googleusercontent.com/wapJD9my47ZbJJZ4LqApX_MbIybbOX-AzEo0BSsvJnImTYmZyn0PP-qUeisLE2tWeJU9f3jS6RBxl1vy9MZ-Te63wpKedVSsldPUBF9sDoepprO-N1_ty51Y-pJbDnB_RIeYeHATJrWE7ja36urj5GM-zhWfqk9Qbl0YlmTDDBNDXm2nmWAP5RX4LID5zg" alt=""><figcaption></figcaption></figure>

<br>


# Typical Network Setup

## 1. Overview

The NNIONGIN supports ﬂexible network setup for different environments. This section describes the typical network topology. The network setup includes:

* **WAN Port Internet Mode**
* **WiFi Client Mode**
* **WiFi AP Mode**

## 2. Use a WAN port to access the Internet

By default, the NNIONGIN is set to use the WAN port to connect to an upstream network. When you connect the NNIONGIN's WAN port to an upstream router, NNIONGIN will get an IP address from the router and have Internet access via the upstream router. The network status can be checked in the **home page**:

<figure><img src="https://lh3.googleusercontent.com/M9LNakWwmfK4fhNsD99ykxfuizNXpQ7GumJ0CLfJt7-l2GkNg-0qDSEA8MWyMHvsCFSnp36NHDQzfUavdLR2p6oSddlSs5NhZHJY3jovqiKOk1tQDgYdFvuRupaHCKZjGCQK9_HTxkJcjEtZvsRn9XUXIPIKRpS2K6pAS-4M-RuWp_b0SN75tbsCwjyleg" alt=""><figcaption></figcaption></figure>

## 3. Access the Internet as a WiFi Client

In the WiFi Client Mode, NNIONGIN acts as a WiFi client and gets DHCP from an upstream router via WiFi.&#x20;

The settings for WiFi Client are under page **System--> WiFi --> WiFi WAN Client Settings**

<figure><img src="https://lh3.googleusercontent.com/TKBdjK6X6gtgBr2CehCIP3V-GFHsOoxODmVFjnBKJSqSOl_PzAfeDcAWtD7eq7AUg_mvuPFfHLxAHETMNZ-LaIas46Az67b24zUTtUpp_u4r3xgvP5jUhMkOAjZIAo2GOF7JrPLvWt4FIP7PtLGv46cYysGFspF0petGEDlDIaECXxIn0Vxb3FTI3Mwcgg" alt=""><figcaption></figcaption></figure>

Enable WiFi WAN Client. In the WiFi Survey Choose the WiFi AP, input the Passphrase, and click Save & Apply to connect.

## 4. Check Internet connection

On the home page, we can check the Internet connection.

* GREEN Tick ![](https://lh5.googleusercontent.com/lGnX8ZvsKaOjGYOT2JdNFfBsIUjpT8HREvbktGSQ0MO95HxlT0xe-YWWsHZPxsc9opf0Fk7v8lakMh8q3Hjb0q9_2e7l0DtZFE6Iml7JGl8ZWuA7JyjmIEZuQyrfCrAAl7e1A9OFYuq7ZUq_YbsUvODTwz3i45syVptv_AUpYpoIG1FAFWjouoqhwKVUlw) : This interface has an Internet connection.
* Yellow Tick ![](https://lh5.googleusercontent.com/_fJOitdDNdJ15AA6K98Gw6tNXxII-AJYqqqjbmzqPkbrSgEjiCQ7Q1yM8A12NcgoGtJ4Bl0irN9unhaif6E6jNMGaH0BzFubbI6K-WCt_2JTimboV8IJ4AQlKSJ4HvmTsmZ3Q3b5sWUYlp896GCRSkGMhN4BlW37-biUb1GsYwv2bG2xYfmB5HQKCaGuZg) : This interface has an IP address but doesn't use it for an internet connection.
* RED Cross ![](https://lh3.googleusercontent.com/zD8GEK7EjNL3im8uiXvaFYu_u3h-xkghfejnYUh6ZhHseeqi5sJ0YTeyjnO0Spuj-F6iJngTIQpKuAzNVl3rnDvDm1EKCSbal59i7eyOJnoaKab-oG2PgHJd5nFNfwTOIpgWsk9Vh1gqf3cSv_NZQUp1edBFjR-1CBDs1_GFXX02a-MpjFR3MVqNT8NVRA) : This interface isn't connected.

<figure><img src="https://lh3.googleusercontent.com/r-c0fW-3pYzstEYtu9taluNIdKrFwP13WPEkIwQ5_8yLIXaWd5PUXozQU8lM56Oe4xLFL6PcADhupP-9ZcxH2UtsK-vaWTfA6EeviuKOv3rApLaGaqOHVj-d9SLetiLVrqR3lpojENVEtkgPNTUi417-cp4C3IU9jLXcokpYZbzoRa1TT4D5NsJqmT2yyA" alt=""><figcaption></figcaption></figure>


# Web Configuration

## 1. Home

Shows the system running status.

<figure><img src="https://lh4.googleusercontent.com/suARFBUJabr92pFf9k7Mj5mjyzLkQuvc7zfItjsakaACj-kn-voQrNB3gUnrt6FBMmpK9SS-30UVFenH2bRnk_EkeT1rgs18LdVylNNYbo5VvOf1-aZzQ4Jv8pRsAly2J3-y_JIcHNXH0Wy-wAReUDAJOSB6NO9mtRlb0QTjflSM0TgkKu34g_vmPC0izg" alt=""><figcaption></figcaption></figure>

## 2. LoRaWAN Settings

Settings to communicate with the Nitro Network LoRaWAN server

<figure><img src="https://lh6.googleusercontent.com/b-KLFDagTVfQYWkJxjfhM22EpmvlkOpXbDhTPnVq6x7UDhyL16tYQUzaSRVuJ2vo7h6ZAW-7QJNI_eKwAfBjLGb384p066oaV7bcgAJ68b13BIG4E344POxsjRfqRXi-3yYRtZIJVplh7p6ZXbQjZJewoPHV52CgLudnv-ezlU4S2bSFgS2X-oMK2m4rTQ" alt=""><figcaption></figcaption></figure>


# Nitro Genesis Node and Staking

#### 1. What is the Genesis Node reward program and what is the reward for it?

The Genesis Node program is a protocol designed to grant NCash holders with a slew of rewards over the next 50 years! As a testament to the loyalty of its community, Nitro Network has opened up a treasure chest of NCash tokens to achieve this goal.

#### 2. What is required to be a Genesis Node?

You need to complete 30 days of stake in the Nitro Staking Program before 15 April,2022. We have passed the above mentioned timeline and Genesis Nodes has already been shortlisted. There are \~498\* Genesis Nodes currently.&#x20;

\*Numbers can be updated subject to Genesis Node validation and verification.

#### 3. Are all NCash holders Genesis Nodes by default?

No. Only those who stake for at least 30 days within the specified date mentioned above are eligible to be a genesis node.

#### 4.**The Genesis Staking Program was extended for two months and has cut the rewards for Genesis Node who staked earlier. Is there any added advantage for early stakers?**

The program has been designed to incentivize all NCash holders who together hold approximately 10 Billion NCash as of today. The idea of the Genesis Node Program is to benefit all our long-term supporters. While the number of eligible nodes are very few even after the extension, we believe there is going to be enough for every Genesis Node. Old qualified Genesis Nodes will not have to worry about sharing rewards as it is a community incentive program and its sole objective is to increase the number of beneficiaries for the program. And the decision of extension to this program was taken as many NCash holders were facing difficulties due to smart contract changes and issues with certain exchanges. The new added numbers are marginal and the benefits are huge. Community is at heart of the entire incentive program and so are Genesis Nodes. In future, for added [incentives](https://nitronetwork.medium.com/nitro-network-genesis-staking-portal-updates-511da0f4dd8a) for Genesis Node, Nitro will keep the early stakers up on the wishlist for beneficiaries.

#### 5. **How many Genesis Nodes are there in total?**

There are 498\* wallets that have qualified for Genesis Node. (\*T\&C apply)

#### 6. **Who can stake on the Genesis Node portal?**

Only Genesis Node can stake on this portal

#### 7. **Can anyone staking now for 30 days become a Genesis Node?**

No. The opportunity to become a Genesis Node is over now. People who are not a Genesis Node can stake their NCash at our Staking portal to earn amazing APR.

#### 8. How many NCash has been allocated to the Genesis Node Program?

4% of Team and Investors reward has been allocated for Genesis Node. That percentage amounts to be 70 Million NCash per month for the next two years before the token halving schedule takes place. The Genesis Staking Portal currently holds 498 wallets\*. And each genesis node can stake upto 10 units where 1 unit = 100,000 NCash. Genesis node earns \~9.62 NCash per unit per epoch.

#### 9. **What is the minimum and maximum amount of NCash one can stake?**

* Minimum is 100,000 NCash&#x20;
* Maximum is 1,000,000 Ncash

#### 10. How is reward getting distributed?

Read our blog on [Genesis Staking](https://nitronetwork.medium.com/nitro-network-genesis-staking-portal-updates-511da0f4dd8a) to understand the distribution in detail.

#### 11. **For how long a Genesis Node will have to Stake?**

The Genesis Node Program will reward the Genesis Nodes for the next 50 Years. So ideally, they can stake for 50 years as per their capability and earn reward accordingly.

#### **12. Is there any lock-in Period?**

No. You can stake and stake your amount anytime. Reward is pro-rata basis (refer question 7)

**13. How often can I claim my rewards?**

Rewards are being allocated per EPOCH (i.e every 30 minutes). So you can claim rewards anytime.


# Nesting

### 1. **What is Nesting?**

Nesting is equivalent to hosting a network. Whoever participates in nesting and becomes a verified host on Nitro Network is called the nester. The Nitro platform enables this process of nesting, creating a synergy among people hosting the network across the world, enabling them to earn from their location. \
Read more here \
1\. <https://nitronetwork.medium.com/nitro-nesting-an-effortless-way-to-earn-from-any-location-in-the-world-9df8777b8a1b2> \
2\. <https://nitronetwork.medium.com/why-nitro-nesting-ensures-everybody-wins-27f041d7c848>

### 2. **Why Nesting?**

"Nesting ensures that we have strong connectivity in a defined radius of coverage area with a minimum number of Nitro ION Miners. It addresses the two prime issues that can stand in the way of earning from a decentralized network. Network congestion - Normally the placement of miners are scattered and unoptimized. This creates network congestion in areas which are densely populated with miners, while there is weak coverage in other areas where there are less miners or no miners at all. Inequitable distribution of rewards- Due to uneven distribution of miners, multiple miners compete for a piece of the same pie when it comes to rewards. By confining the radius and limiting the number of miners per radius, we are not only optimizing the resource utilization but also making sure every participant gets maximum rewards.&#x20;

Read more here: <https://nitronetwork.medium.com/why-nitro-nesting-ensures-everybody-wins-27f041d7c848>

### **3.** Who is a Nester?

Anybody who hosts the Nitro Network is a Nester. You can host your "nest" through the Nitro Platform anywhere in the world. You become a Nester when your location/address is verified and approved by the Nitro Network platform by fulfilling the required criteria.

### 4. Why should you become a Nester?

Becoming a Nester on Nitro Network has many benefits.

1. You can earn NCash effortlessly
2. Your location is your source of wealth.
3. It requires minimum investment. All you require is a small, unutilized space in your home/office, good WiFi connectivity and power supply.

### 5. What are the steps for becoming a Nester?

You can become a Nester in 4 simple steps:&#x20;

1. [Register](https://ecosystem.nitro.network/nest) your location of hosting Nitro Ion Miner&#x20;
2. Complete the [KYC verification process](https://ecosystem.nitro.network/myaccount/mynest) for your eligible&#x20;
3. Nitro will verify your location based on your KYC data&#x20;
4. Pay refundable security deposit to receive your hosting device- Nitro ION Miner&#x20;

Become a “nest"

### 6. How many Nesters will be there?

In Phase 1, we are deploying Nitro ION Miner to 1000 Nests in cities of the USA and India and these are tier-1 cities.&#x20;

1. United States (Los Angeles (CA), Miami (FL), New York City (NY))&#x20;
2. India (Hyderabad, Mumbai, Bengaluru, Chennai, Delhi)

### 7. When will the Nesting KYC for other cities begin?

Upon successful completion of deployment to the first 1000 Nesters, we will start phase 2 and will open the KYC process for other cities. But make sure you register today only, registration is open for all. Announcements will be made on our social channels for the same.

### 8. Do Nesters in specific locations have more benefits?

Nesting rewards are based on location. We have categorized cities into a Tier structure based on certain parameters such as population, infrastructure, footfall etc. More precisely, cities are categorized into Tier 1 (Iconic Tier) , Tier 2 ( Premium Tier) and Tier 3 (Top Location) in descending order. This means, if your current location falls in the Tier 1 category your rewards will be optimized as compared to Tier 2 or Tier 3 locations, simply by being in a prime location. There are rewards for Tier 2 or Tier 3 locations too! We have built the Tier structure in a way where everybody wins!

### 9. Can there be multiple Nesters in the same place?

No. There can be only 1 Nester in a radius of 1 km

### 10. How much does a Nester earn?

The first 1000 Nesters of phase 1 will earn \~182 NCash per EPOCH (This is potential reward and subject to many factors related to Nesting. If the number of Nesters change, reward may vary as well).


# Nitro Bot Army Whitelist

### 1. What is Nitro NFT Whitelist?

[Nitro NFT Whitelist](https://nft.nitro.network/) is a process of shortlisting wallet addresses with priority access to an NFT collection before making it available to the general public. Please note: Following all the steps will just qualify you to be eligible to win a whitelist spot, it's not a guarantee. A Whitelist spot will be given after validating your entries and activities.

### 2. Why should I whitelist for Nitro NFT?

With Nitro NFT whitelisting, you will get an NFT at 0.05 ETH

### 3. By when do I have to whitelist?

Whitelisting will start from 10, Feb'23 ( 10:00 AM UTC) and will be active till 17, Feb'23 (10:00 PM UTC). Early whitelisting is suggested as the shortlist will happen based on First Come, First Serve (FCFS) basis

### 4. When will the whitelist process end?

It will end on 17, Feb'23 (10:00 PM UTC)

### 5. What is the timesheet for the Whitelist process?

| Whitelist Information                                            | Date          |
| ---------------------------------------------------------------- | ------------- |
| Whitelist starts                                                 | 10th Feb 2023 |
| Whitelist Closes                                                 | 17th Feb 2023 |
| Release first list of whitelist (WL) spot winner with pay option | 18th Feb 2023 |
| Close pay option for 1st set of whitelist winner                 | 22nd Feb 2023 |
| Release second list of winner                                    | 23rd Feb 2023 |
| Close pay option for 2nd set of whitelist winner                 | 25th Feb 2023 |
| Minting for whitelists                                           | 27th Feb 2023 |
| Return money to non-WL                                           | 27th Feb 2023 |

### 6. How to get a whitelist spot?

Complete the whitelist process by doing all the [cool tasks](https://nft.nitro.network/)

### 7. What is the selection process?

People who come first and complete all the optional and mandatory tasks of whitelisting successfully will have a high chance of getting a whitelist spot.&#x20;

### 8. If I don't pay 0.01 ETH USDT, is there any chance of getting a whitelist spot?

You may get, chances are less. Paying 0.01 ETH is optional. However, people who pay will be given priority and have a high chance of winning a WL spot

### 9. Can I apply for more whitelist spots?

Yes, You will have to pay 0.01 ETH x no. of WL spot you want to apply for. Pay in multiples of 0.01 ETH. For example- if you want to apply for 3 whitelist spots, 0.03 ETH in total. Any partial payment will lead to disqualification.

### 10. How many whitelist spots are there in total?

800

### 11. Let's say I paid 0.01 ETH but didn't get the WL spot, then when will I get my money back?

You will get it on 27th Feb in the same wallet address from which you have paid. Please note that you will get 0.01 ETH irrespective of market volatility and price,. For further timeline requirements, please check visit question 5.

### 12. In case I win the whitelist spot, In how many days do I have to pay?

1st set of winners will be released on 18 Feb and the payment option will be enabled till 22nd Feb. You will get 5 Days to pay and own your NFT

### 13. In case, I don't pay within the mentioned timeline, what will happen to my spot and money?

You will lose your spot and your spot will be given to the next eligible whitelisted in the second list. Your money will be returned.&#x20;

### 14. Will there be two lists of Whitelist spot winners?

If the Whitelist spot winner from the first list doesn't complete their payment within the given timeline, their spot will be made available for the next set of eligible whitelists.&#x20;

### 15. Where can I read more about Nitro Network?

Please visit our website: <https://nitro.network/>&#x20;

### 16. I have performed all the tasks, what else can I do to increase my chance of getting a whitelist spot?

Refer the whitelist to your friends and onboard them. The more you refer, the more points your earn and get closer to winning a whitelist spot.


# NFM (Origin NFTs)

### 1. Is Nitro Bot Army a new NFT collection offered by Nitro Network?

Yes. Read more about Nitro Bot Army [here](https://medium.com/@nitronetwork/nitro-bot-launch-unlocking-a-new-era-of-utility-1ea333af2c8a).

### 2. How many NFTs are there in this new Nitro Bot Army collection in total?

The total supply is 10,000 NFTs

### 3. Will all 10,000 NFTs be available for sale?

These 10,000 collections will be listed for sale in 5 mint. The number of NFTs in each mint will differ.

### 4. Is it on the Avalanche chain?

No. It will be on the Ethereum chain. Ethereum has a vast NFT community and we would like to expand our ecosystem to NFT lovers of Ethereum Chain.

### 5. Where will it be listed for public sale?

It will be listed on Opensea only for public sale.

### 6. When will it be listed for public sale?

On 28th Feb

### 7. Is there any whitelist program to get the NFT before the public sale?

Yes, find the details at - <https://nft.nitro.network/>&#x20;

### 8. What benefits does a whitelist get?

The [NFT whitelist](https://nft.nitro.network/) gives you early access to Nitro Bot NFTs at a lower price.

### 9. Nitro Network launched NFM (Non-fungible miner) as a digital miner in the form of NFT in 2022. What will happen to those?

We have minted 2500+ NFM so far. These NFMs will be referred to as Origin NFTs. Our Origin NFT will continue to enjoy high rewards per EPOCH by staking.

### 10. What is the difference between the Nitro Bot Army collection and NFM (Origin NFTs)?

Nitro Bot Army is the second generation of NFMs (Origin NFTs). NFMs (Origin NFTs) are on the Avalanche chain while Nitro Bot Army will be on Ethereum. Second, NFMs (Origin NFTs) will earn higher rewards upon staking to our platform (currently ICONIC earns \~96 NCash, PREMIUM earns 80 NCash and TOP earns 24 NCash per EPOCH), Nitro Bot Army collection will earn between 10–15 NCash per EPOCH\* upon staking and will earn other rewards through community programs and airdrops. Also, NFM (Origin NFTs) will enjoy the Network Data transfer reward allocated for them, unlike Nitro Bot Army.

### 11. Will NFM (Origin NFTs) get the benefits of utilities offered under the Nitro BoT Army collection?

Yes, NFM (Origin NFTs) will get all the benefits of utilities that the Nitro BoT Army has. But in order to participate in certain community programs and airdrops they will need Nitro Bot Army NFTs. More details regarding these programs will be released later when the programs go live.

### 12. Will NFM (Origin NFTs) no longer be available for sale?

NFM (Orgin NFTs) will be the highest reward-earning NFT of Nitro Network. These are available in limited numbers now and for a limited time period. After these, Origin NFT will not be up for sale. Grab them [here.](https://nitro.network/buy-nfm)

### 13. Explain the reward distribution between NFM (Origin NFTs) and Nitro Bot Army.

| Network Infrastructure Mining Reward pool for NFTs | (80% allocated to NFTs) | 869,200,000 NCash |
| -------------------------------------------------- | ----------------------- | ----------------- |
|                                                    | NFMs                    | Nitro Bot Army    |
| Pool Allocation                                    | 50%                     | 50%               |
| ICONIC (60%)\*                                     | 260,760,000 NCash       | 434,600,000 NCash |
| PREMIUM (38%)\*                                    | 165,148,000 NCash       |                   |
| TOP (2%)\*                                         | 8,692,000 NCash         |                   |
| Total                                              | 434,600,000 NCash       | 434,600,000 NCash |

**\*T\&C:**

1. Considering the limited number for NFM (Origin NFTs) the percentage allocation for different category of NFMs have been updated. A higher percentage has been allocated to ICONIC (from 42% to 60%) and PREMIUM (from 33% to 38%) to benefit our early joiners. TOP has been minted less in number, hence allocation has been reduced for that.
2. These allocation are subject to change with mint process and new drops.


