> For the complete documentation index, see [llms.txt](https://mhnt.gitbook.io/metahunt-wp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mhnt.gitbook.io/metahunt-wp/staking-mechanics/eth-divis.md).

# (ETH) Divis

In the MetaHunt ecosystem, 10-20% of ticket sales are allocated to be distributed among COC token holders who choose to stake their tokens. This feature establishes a system where token holders can reap the benefits of the game's success, while also fostering a thriving and engaged community.

To provide a clear understanding of this distribution mechanism, let's consider a scenario where $1,000 worth of ETH in ticket sales are generated in a single round. Based on the predetermined percentage, between $100 and $200 would be set aside for distribution among staking token holders. The share each holder receives will be proportionate to the amount of their staked tokens.

The distributed ticket sales system serves as an incentive for token holders to stake their COC tokens. By doing so, they can enjoy the rewards generated through ticket sales, further enhancing the value of their investment in the project.

Overtime, as more games start to take place simultaneously, and as we move to automate all the gaming mechanics, we can expect to have multiple ticket sales ongoing at the same time, bringing more back to token stakers.


---

# 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://mhnt.gitbook.io/metahunt-wp/staking-mechanics/eth-divis.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.