> For the complete documentation index, see [llms.txt](https://whitepaper.bountykinds.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.bountykinds.com/token-ecosystem/dominion-ranking.md). # Dominion Ranking BOUNTYKINDS rewards player skill and effort with its unique triple token system. Balance between the tokens you can earn from is kept at a steady level. Because each token limits one of the other, the only way players could be rewarded a good amount is either by winning a lot of games with heavy skill expression, or by grinding numerous matches and accumulating as much BWP as possible. Based on the total daily BWP earned daily in each game, the daily ranking will fluctuate and the amount of rewards will constantly change. [Dominion ranking reward](/token-ecosystem/dominion-ranking/rewards.md) Various rewards for each game are also drop in different amounts depending on the ranking. This gaming environment means that having strong NFTs does not automatically guarantee high income. Meaning players who start on low level NFTs have an equal shot at getting a higher ranking on the ladder as those who pre-purchased NFTs. If you play hard, you earn more - that is the main philosophy of BOUNTYKINDS. --- # 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://whitepaper.bountykinds.com/token-ecosystem/dominion-ranking.md?ask=&goal= ``` `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.