> For the complete documentation index, see [llms.txt](https://litepaper.pixels.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://litepaper.pixels.xyz/staking-ecosystem-and-token-mechanics/staking/decentralized-publishing.md). # Decentralized Publishing Unlike typical staking, Pixels staking involves directly selecting games to support. Stakers allocate their tokens into individual "game pools," effectively voting on which games deserve ecosystem incentives and resources. The amount staked into each game influences the share of emissions and incentives that game receives in the future, fostering competition among games. **Competitive Publishing Environment:** * Games compete to attract stakers by demonstrating strong player retention, high net in-game spending, and effective use of ecosystem tools * Staking allocations serve as a clear signal from the community on game quality and ecosystem contribution **Reward Calculation:** * Each game pool distributes rewards based on the proportion of total $PIXEL staked to it. * Games individually determine their reward contributions to their stakers, ideally aiming to be competitive to attract more stakers * Rewards are periodic, transparent, and governed by a clear mathematical model --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://litepaper.pixels.xyz/staking-ecosystem-and-token-mechanics/staking/decentralized-publishing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.