> 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/nectar-burn-deflationary-engine-and-buy-back-system.md).

# NECTAR BURN: Deflationary Engine & Buy-Back System

Key Mechanics:

1\. Distribution Trigger

     ○ After PLS is collected via Hive, the Nectar Burn contract receives its share.

     ○ A public function must be called to initiate distribution. This function can be

executed by any user and rewards the caller for participation.

2\. Automated Burn Window (Every 15 Minutes)

     ○ Every 15 minutes, the system becomes eligible to burn $769 worth of HONEY

using accumulated PLS.

     ○ If no one triggers the function during a window, the amount is carried forward to

the next period, increasing the burn power.

3\. Scheduled Purge Events

     ○ Starting on Day 69 from the BeeHive launch, and then every 99 days, a Nectar

Purge event occurs.

     ○ The total available PLS is split into 100 equal portions, each callable every 15

minutes to execute buy-and-burn actions.

4\. Buy & Burn Logic

     ○ PLS allocated to Nectar Burn is used to purchase HONEY tokens from DEX.

     ○ The purchased tokens are permanently burned, reducing supply and creating a

deflationary environment.


---

# 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/nectar-burn-deflationary-engine-and-buy-back-system.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.