> 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.md). # Staking > **One token. Many “validators.” The validator is the game.** Pixels introduces a decentralized publishing model powered by staking, where games themselves replace traditional validators. Instead of securing transactions on a blockchain, stakers participate directly in determining which games receive resources and incentives from the Pixels ecosystem. This model decentralizes publishing decisions, aligns incentives across players and developers, and creates a sustainable competitive environment. ### Why Stake? **Strategic Benefits:** * **Attractive Rewards:** Each game pool offers periodic rewards reflecting game performance. * **Influence Ecosystem Direction:** Stake allocations drive future incentive decisions and ecosystem focus. * **Risk Management:** Diversify across multiple game pools to manage exposure and risk. * **Ecosystem Security:** Your participation helps secure and strengthen the overall Pixels ecosystem by incentivizing games to contribute valuable data, utilize ecosystem tools, and maintain healthy economics. --- # 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://litepaper.pixels.xyz/staking-ecosystem-and-token-mechanics/staking.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.