> For the complete documentation index, see [llms.txt](https://docs.powercity.io/beehive/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.powercity.io/beehive/workflow-and-participation-mechanics/beekeeper-long-term-staking-and-reward-generation.md). # BEEKEEPER: Long-Term Staking & Reward Generation Key Mechanics: 1\. Staking Options ○ Users can stake any amount of HONEY. ○ Minimum staking period: 69 days ○ Maximum staking period: 1,869 days 2\. Reward Intervals Rewards are distributed at three distinct intervals for active stakers: ○ Every 9 days ○ Every 81 days ○ Every 243 days 3\. HoneyComb Elite Ticket Eligibility ○ Users who stake in multiples of 10,000 HONEY tokens for the maximum duration (1,869 days) qualify for HoneyComb Elite Tickets. ○ 1 ticket is awarded per 10,000 HONEY locked for the max duration. 4\. Reward Distribution Visibility ○ Rewards are not distributed automatically. ○ Once the distribution is triggered on the Nectar Burn page, the rewards are: ■ Calculated and reflected on the Harvest page ■ Available for claiming by users from either the BeeKeeper or Harvest interface. --- # 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.powercity.io/beehive/workflow-and-participation-mechanics/beekeeper-long-term-staking-and-reward-generation.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.