> For the complete documentation index, see [llms.txt](https://docs.stratovm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stratovm.io/node-operations/node-license/pricing-and-purchasing.md).

# Pricing & Purchasing

## Overview

Owning at least 1 Node License is a requirement for receiving rewards from operating a StratoVM Node. The more Node Licenses associated with your wallet address, the greater your share of the overall $SVM rewards.

## Where To Purchase

Node Licenses are not yet available for sale. Please follow [@StratoVM\_ ](https://x.com/StratoVM_)on Twitter for more details.

Node Licenses will be available to purchase starting August 29th for the public. A whitelist sale will begin August 27th and last 48 hours for those that quality.

## Pricing Tiers

Node Licenses are available for sale in different pricing tiers. There is no difference between the functionality of Node Licenses between different pricing tiers. As more Node Licenses are sold and enter circulation, the price for new node to enter circulation and further dillute operator rewards increases.

Here's the pricing tier table, Node Licenses sales will start at Tier 1 and increase in tier when the entire quantity of the current tier is sold.

| Tier        | Available Quantity | Price (Eth)  |
| ----------- | ------------------ | ------------ |
| **Tier 1**  | **2,387**          | **0.05 Eth** |
| **Tier 2**  | **2,268**          | **0.06 Eth** |
| **Tier 3**  | **2,155**          | **0.07 Eth** |
| **Tier 4**  | **2,047**          | **0.08 Eth** |
| **Tier 5**  | **1,945**          | **0.09 Eth** |
| **Tier 6**  | **1,847**          | **0.1 Eth**  |
| **Tier 7**  | **1,755**          | **0.12 Eth** |
| **Tier 8**  | **1,667**          | **0.13 Eth** |
| **Tier 9**  | **1,584**          | **0.15 Eth** |
| **Tier 10** | **1,505**          | **0.18 Eth** |
| **Tier 11** | **1,450**          | **0.20 Eth** |
| **Tier 12** | **1,400**          | **0.23 Eth** |
| **Tier 13** | **1,350**          | **0.27 Eth** |
| **Tier 14** | **3,101**          | **0.31 Eth** |
| **Tier 15** | **7,541**          | **0.35 Eth** |
| **Tier 16** | **9,555**          | **0.41 Eth** |
| **Tier 17** | **11,702**         | **0.47 Eth** |
| **Tier 18** | **12,500**         | **0.54 Eth** |
| **Tier 19** | **12,333**         | **0.62 Eth** |
| **Tier 20** | **12,300**         | **0.71 Eth** |
| **Tier 21** | **12,250**         | **0.82 Eth** |
| **Tier 22** | **12,199**         | **0.94 Eth** |
| **Tier 23** | **12,020**         | **1.08 Eth** |
| **Tier 24** | **11,980**         | **1.24Eth**  |
| **Tier 25** | **11,970**         | **1.43 Eth** |
| **Tier 26** | **11,701**         | **1.65 Eth** |
| **Tier 27** | **11,589**         | **1.89 Eth** |
| **Tier 28** | **8,902**          | **2.18 Eth** |
| **Tier 29** | **2,987**          | **2.50 Eth** |
| **Tier 30** | **2,010**          | **2.88 Eth** |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.stratovm.io/node-operations/node-license/pricing-and-purchasing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.