# REVENUE SHARING {% hint style="info" %} Coming Soon! {% endhint %} \ As part of our commitment to community enrichment, we are excited to introduce a dedicated Revenue Sharing Program tailored for $HORUS token holders. This initiative is designed to empower and reward members of our community who actively contribute to the success and growth of our ecosystem. ## Requirement To qualify for participation in this exclusive program, community members must meet the following criteria: * Participants must hold a minimum of XX,XXX $HORUS tokens. The specific threshold for eligibility will be announced in due course, ensuring transparency and fairness in the qualification process. * Holders are required to link their $HORUS token-holding wallet to our forthcoming dashboard. This step ensures accurate verification and allows for easy reward claims.\ \ Rewards Dashboard will be developed on the second phase of our [roadmap](/horus/about-us/roadmap.md) to simplify the process and enhance your participation in the Revenue Sharing Program. ## Summary This initiative not only encourages community engagement but also aligns with our overarching goal of creating a symbiotic relationship between our project and its supporters. Stay tuned for further details on the precise token holding requirement and additional benefits that will be extended to our valued $HORUS token holders through this innovative Revenue Sharing Program. Together, we aim to foster a thriving and mutually beneficial community ecosystem. --- # 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://eye-of-horus.gitbook.io/horus/the-token/revenue-sharing.md?ask= ``` 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.