# Workflow and Participation Mechanics

The BeeHive Protocol operates on a cycle-based system, where each cycle lasts **one** day. Participation and rewards are managed through a series of steps:

**a**. **Initial Participation Requirements**

* M**inimum Investment**: To participate in the BeeHive Protocol, users must hold a minimum of **100K PLS tokens**. PLS is a prerequisite for participating in the protocol's activities.

**b. Purchasing Flowers and Bees**

* **Buying Flowers**: Users purchase flowers, selecting from different types available. The type and number of flowers influence the amount of tokens required for participation and determine the user's Hive share allocation.
* **Buying Bees**: Users also buy bees, essential for pollination activities within the protocol. The number of bees purchased affects the token payment and Hive share assignment.

**c. Cycle Completion and Rewards**

* **Cycle Duration: Each participation cycle lasts 1 day.**
* **Earning Honey Tokens**: Upon the completion of a cycle, participants receive their earned **HONEY Tokens** based on their Hive share and the cycle’s performance.

**d. Honey Token Claiming Options**

Participants can manage their earned Honey Tokens:

* **Claim HONEY**: Directly claim the earned Honey Tokens to your wallet. Exchange the Honey Tokens on a Decentralized Exchange for other cryptocurrencies or Stake in Beekeeping.

**Note: The user won’t be able to claim the HONEY Token for the first 3 days.**


---

# Agent Instructions: 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:

```
GET https://docs.powercity.io/beehive/workflow-and-participation-mechanics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.