> For the complete documentation index, see [llms.txt](https://toyland-2.gitbook.io/toyland-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://toyland-2.gitbook.io/toyland-docs/usdtoy/tokenomics.md).

# Tokenomics

The native cryptographically-secure fungible protocol token of Toyland (ticker symbol $TOY) is a transferable representation of attributed utility functions specified in the protocol/code of Toyland, and which is designed to be used solely as an interoperable utility token thereon.

$TOY provides the economic incentives which will be distributed to encourage users to exert efforts towards contribution and participation in the ecosystem on Toyland, thereby creating a mutually beneficial system where active participants are fairly compensated for their efforts. $TOY is an integral and indispensable part of Toyland, because without $TOY, there would be no incentive for users to expend resources to participate in activities or provide services for the benefit of the ecosystem. Given that additional $TOY will be awarded to a user based only on its actual usage, activity and efforts made on Toyland and/or proportionate to the frequency and volume of transactions, users of Toyland and/or holders of $TOY which did not actively participate will not receive any $TOY incentives.

#### 📊 Tokenomics Overview

The platform operates a $TOY reward pool which distributes $TOY to incentivise active players, regardless of game outcomes. Skilful players / winners would be eligible to receive more $TOY rewards.

Further, as a network effect, users may keep their $TOY in their wallet and utilise in a peer-to-peer manner with any player, third party or platform, e.g. private games.

$TOY functions as an access token granting users access to selected products or services, for example certain premium functionalities, exclusive products/services, priority for events, or greater or more unique transaction rewards.

<table><thead><tr><th width="349.41015625">Allocation Category</th><th width="149.859375">Percentage</th></tr></thead><tbody><tr><td><strong>Ecosystem/ Commuunity</strong></td><td><strong>70%</strong></td></tr><tr><td><strong>CEX Marketing, Partnership, KOL</strong></td><td><strong>7%</strong></td></tr><tr><td><strong>Liquidity</strong></td><td><strong>9%</strong></td></tr><tr><td><strong>Strategic Reserve</strong></td><td><strong>2.67%</strong></td></tr><tr><td><strong>Foundation</strong></td><td><strong>6.33%</strong></td></tr><tr><td><strong>Team</strong></td><td><strong>5%</strong></td></tr></tbody></table>

***

#### 🪙 Total Supply

**100,000,000 TOY**


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://toyland-2.gitbook.io/toyland-docs/usdtoy/tokenomics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.