> For the complete documentation index, see [llms.txt](https://docs.ferrisgames.com/overview/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ferrisgames.com/overview/tokenomics/psyker-staking.md). # Psyker Staking ![](/files/ipRoS9moQO3mwe0Ov46w) Psyker has allocated initial token supply for $PSYK Token (1,000,000 $PSYK) to Keycard holders who are staking. We want to incentivize early adopters by allowing them to pre-mine a portion (or all) of the initial rewards token supply via NFT Keycard and NFT Hideout staking until Open Beta Launch. The stakers will earn a pre-PSYK token (Locked Reward) that will be redeemed for PSYK token 1:1 after Open Beta Launch. 10,500 total NFTs can be staked (Keycards and Hideouts) with 6 rarities (reward levels). Earning a minimum of 1 per day. Stakers need at least 1 Keycard staked in order to stake Hideouts. **Keycard & Hideout Reward Rate:** * Common: 1 $PSYK/Day * Uncommon: 1.1 $PSYK/Day * Rare: 1.2 $PSYK/Day * Epic: 1.3 $PSYK/Day * Legendary: 1.4 $PSYK/Day * Mythic: 1.5 $PSYK/Day No halving mechanism, rewards will extinguish once 1,000,000 tokens have been mined before TGE. The rewards pool and staking will be reconfigured for future releases. --- # 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://docs.ferrisgames.com/overview/tokenomics/psyker-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.