> For the complete documentation index, see [llms.txt](https://coinlive.gitbook.io/xr-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coinlive.gitbook.io/xr-whitepaper/05-tokenomics/5.1-xraders-xr.md). # 5.1 XRADERS (XR) The ultimate aim of the XRADERS project is to develop a decentralized trading and gaming protocol, harnessing the power of the community to redefine cryptocurrency trading. At the heart of this community-centric approach is the $XR token, pivotal in driving engagement and governance within the XRADERS ecosystem. In addition to enhancing the gaming experience on the platform, the $XR token serves three critical functions: fostering community engagement, facilitating governance operations, and empowering users within the XRADERS environment. $XR is XRADERS's governance token, with a total issuance of only 100,000,000 XR tokens. * Token Name: XRADERS * Token Ticker: $XR * Contract: * Total Issue: 100,000,000 XR * Token Distribution Plan : [Link](https://docs.google.com/spreadsheets/d/1it83DJrvmUgBjmd5WcCQVFe41bwgcXdTGt-y25GhM8s/edit?usp=sharing)
Refer to --- # 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://coinlive.gitbook.io/xr-whitepaper/05-tokenomics/5.1-xraders-xr.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.