> 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/hive-daily-participation-and-honey-generation.md). # HIVE: Daily Participation & HONEY Generation Key Mechanics: 1\. Daily Cycle ○ Hive operates on a 24-hour cycle. ○ Each cycle resets automatically every day. \ 2\. User Participation ○ Users participate by depositing PLS and selecting the number of Flowers and Bees, which determine their allocation share. ○ Participation is open to all, encouraging daily engagement and decentralised contribution. \ 3\. Reward Claiming ○ At the end of each cycle, users can claim their HONEY tokens based on their share of contributions. 4\. Post-Claim Options ○ Claimed HONEY can be: ■ Sold or traded on Decentralised Exchanges (DEX), or ■ Staked in the BeeKeeper contract to earn longer-term protocol rewards. 5\. PLS Distribution to Ecosystem Contracts ○ All PLS deposited in Hive is allocated to various contracts. ○ Distribution must be manually triggered via a public function on the Nectar Burn page. ○ The caller is rewarded with a portion of the ecosystem's reward pool, incentivising community participation. --- # 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/hive-daily-participation-and-honey-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.