> 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/tokenomics-and-distribution.md).

# Tokenomics and Distribution

The economic model of the BeeHive Protocol is designed to ensure sustainability, reward participation, and support long-term growth. Here's how the **PLS Token** distribution is structured:

* **Total PLS Distribution**:
  * **12% TEAM**: Allocated to the team members for their efforts in building and maintaining the protocol.\
    \*\*\*8.33% of the TEAM token distribution is allocated to CORE ($WATT stakers), which corresponds to 1% of each deposit made into the Hive.
  * **24% Nectar Burn**: Tokens are permanently removed from circulation to reduce supply and potentially increase value.\
    \*\*\*20% of **Nectar Burn** goes to Nectar Purge
  * **64% Rewards in Beekeeping**: Distributed as rewards to participants who stake their Honey Tokens, fostering active engagement.


---

# 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/tokenomics-and-distribution.md?ask=<question>&goal=<endgoal>
```

`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.