> 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/how-to-stake/in-game-staking.md). # In-Game Staking If a player has Pixel in-game, we will simulate staking on their behalf!\ \ Players can stake their in-game balances of $PIXEL directly, provided they meet: * A minimum balance of 100 $PIXEL. * An active login within the last 30 days. ### **Land-Boost Feature** Players who hold Farm Land NFTs gain additional staking power calculated by: STAKING\_POWER = STAKED + \[NUM\_LANDS × min(STAKED × 10%, 100000)] * STAKING\_POWER: Total staking amount including land-based bonuses. * STAKED: Base amount of $PIXEL tokens staked. * NUM\_LANDS: Number of Farm Land NFTs owned. Essentially, each Farm Land NFT will give a 10% staking power boost to Pixel in-game. However the max amount of staking power per Farm Land caps out at 100,000 $PIXEL (1,000,000 $PIXEL would be needed to hit that cap). ### Distribution Cadence At first in-game the in-game staking distribution cadence will happen on a monthly basis, but will move to a daily cadence in the near-future. --- # 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/how-to-stake/in-game-staking.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.