# Tokenomics

Tokenomics encompasses the comprehensive framework and operational mechanics of 2 tokens within the ecosystem. It covers aspects such as the distribution of tokens, the interplay of supply and demand, the token's utility and role within the ecosystem, incentives offered to stakeholders, governance structures, and the strategies for capturing and distributing value. This document offers a transparent overview of the tokenomics associated with Sp8de.

<figure><img src="/files/0i9AZrTWygmuHvc53duB" alt=""><figcaption></figcaption></figure>

**What is the purpose of the SPX token in the blockchain?**  It is a system token that allows the use of system resources (RAM, CPU, NET) on the network.

**What is the circulation supply and the amount of tokens that the team hold?**  The total supply of SPX is 8,888,888,888.00 tokens.  The team has reserved a 1B for marketing and business development purposes. All other tokens are in hands of ICO supporters since 2018.<br>

**What is the purpose of the QRNG token in the blockchain?** To purchase quantum randomness and further lift restrictions imposed by the SPX token. And with time the token will be movable across multiple blockchains as the project progresses. &#x20;

**How many QRNG tokens will be issued in total, and how many per day?** The maximum quantity is not limited. Daily: 201,600 payments (1 payment = 5 QRNG = 1 purchase) = 1,008,000 QRNG per day, not counting the tokens that will be burned (which we cannot calculate), but no more than 10% of the total amount. For the generator, it is once per block (0.5 Second); for the validator, it is once every 6 blocks (3 seconds).<br>


---

# Agent Instructions: 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:

```
GET https://sp8de-docs.gitbook.io/s-p-8-d-e-or-white-paper/tokenomics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.