> For the complete documentation index, see [llms.txt](https://arbiter-nft.gitbook.io/arbiter-white-paper-v.1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://arbiter-nft.gitbook.io/arbiter-white-paper-v.1/tokenomics.md).

# Tokenomics

Even in our case, with a functioning and revenue-generating product line, a wrong Supply strategy could make our NFT virtually worthless.

**So why 3,000 and not more**?

First of all, our Reward System does not need venture investment, because it's already operational.

Second. The idea behind ARBITER is to build an efficient diversification tool and a store of value through a single NFT. The limited supply is conducive to this goal.

Third. We strongly believe 3,000 NFTs is closer to what the Cardano NFT market can absorb at this moment.

Some may argue that a bigger supply would increase our overall visibility.

We are aware of this. However, we do have big plans in place to grow our brand image without affecting the supply dynamics.

<figure><img src="/files/dYsAdTTUXNHekDt5oJ4H" alt=""><figcaption></figcaption></figure>


---

# 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://arbiter-nft.gitbook.io/arbiter-white-paper-v.1/tokenomics.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.