# $OCO Tokenomics

The $OCO tokenomics are designed to foster a stable and thriving ecosystem within the OCO online casino. 7,777,777,777 $OCO tokens will ever be created, ensuring scarcity and potential value appreciation. 100% of tokens are allocated on launch, promoting fairness and immediate accessibility.

Here’s a breakdown of the distribution:

* Liquidity Pool (75%)

A significant portion of the tokens are allocated to the liquidity pool. This ensures sufficient liquidity for smooth trading on decentralized exchanges (DEXs), contributing to token stability.

* Marketing & Community Building (15%)

To ensure widespread adoption and a vibrant community, 15% of tokens are dedicated to marketing efforts. This includes raising awareness, attracting users, and fostering community engagement.

* Game Development (5%)

A designated allocation is reserved for ongoing game development within the casino. This fuels the creation of new features, functionalities, and improvements to enhance the player experience.

Here’s a graph explaining the tokenomics of the OCO token:

| Liquidity pool (LP)          | 5,833,333,332 | 75% |
| ---------------------------- | ------------- | --- |
| Marketing wallet             | 1,166,666,666 | 15% |
| Development for games wallet | 388,888,888   | 5%  |
| Team wallet                  | 388,888,888   | 5%  |

By implementing this transparent distribution model, OCO prioritizes long-term sustainability and fosters a thriving ecosystem for token holders, players, and the overall OCO platform.

<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://owners-casino.gitbook.io/oco-whitepaper/usdoco-token/usdoco-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.