> For the complete documentation index, see [llms.txt](https://xorion-chain.gitbook.io/xorion-chain-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xorion-chain.gitbook.io/xorion-chain-docs/the-xor-token/token-emission.md). # Token Emission Rather than relying on inflation to fuel growth, we take a smarter approach, carefully timing emissions sighted with actual network usage, staking demand, and community incentives. There are no open-ended mint functions. Every XOR token that will ever exist is already accounted for. XOR emissions are led by a pre-allocated, multi-year release schedule, adjusted with: * Vesting timelines * Staking rewards and incentive programs * Liquidity mining and ecosystem growth grants Tokens enter circulation gradually over several years, ensuring a steady flow of liquidity. There is no inflationary minting mechanism, no supply dilution, and no backdoors. Every release is scheduled, visible, and subject to the rules embedded in the protocol. From the 35% allocated to Ecosystem & Community Incentives, emissions will roll out through liquidity mining events, airdrops, and builder grants. These emissions are tied to milestones, community programs, and governance-approved campaigns. Tokens won’t just be handed out; they’ll be earned through contribution, participation, and in line with Xorion’s mission. In a space plagued by inflationary shortcuts, Xorion does things differently. Every XOR token is considered. Every emission is earned, unlocked, or bonded. This is a token model that values trust, transparency, and long-term distribution. --- # 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://xorion-chain.gitbook.io/xorion-chain-docs/the-xor-token/token-emission.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.